Five tools at the panel.
One drawer in the chest.
Calls and messages with their work context attached: the line your crew dials, the SMS thread the homeowner replies to, and the recording-enabled workflows your company turns on, kept with the customer and job record.
The pains the founder built it against.
- 01.The cold-call tool charging $80 per seat that was wrong about every name in it. The contact data didn't reconcile with the CRM, the dialer logged calls to a place no one read, and the operator paid four times for the same work.
- 02.The call recording an inspector asked for after a contested install — and nobody could say where it lived, who had access, or whether the customer had been told it was being recorded.
- 03.The 27-minute discovery call that got summarized as 'looks promising' in a CRM note nobody else read, and the deal that died because the next person on the account had no idea what was discussed.
- 04.TCPA, 10DLC registration, recording-consent rules that vary by state — compliance the operator was technically responsible for and practically had no tooling to handle.
The tools that ship together.
Telnyx-backed softphone. Click-to-call from any contact in the chest. Caller ID by job site, by office, or by personal cell — operator's choice. Press-1 routing for outbound dialing campaigns. Real numbers, not VOIP that fails callbacks.
Pre-registered 10DLC campaigns. Compliant message templates. Two-way SMS threading attached to the project record. Opt-out handled automatically; the contact never has to be told twice.
Recording is a per-company setting, and a recording disclosure is played on the call before recording proceeds.
Recorded calls can land in the record with a short summary, action items for the project log, and a draft follow-up email for the operator to edit. The summary lives next to the recording.
On the menu.
The honest answers,
without the sales gloss.
Recording rules vary — one-party consent in some states, all-party consent in others. Torch defaults to operator consent prompts for inbound calls in two-party states and prompts for outbound where the called party has not previously consented. The defaults are conservative; the configuration matches your firm's compliance posture rather than the platform's. State law is the law; tooling is what makes it followable.
Forge handles 10DLC campaign registration through Telnyx. Approval times vary (typically 1–4 business days for a low-throughput business campaign). During approval, outbound SMS is throttled per the carrier's rules; once approved, throughput increases. The Forge team handles the registration paperwork; the operator approves the use cases and content templates.
Yes. Numbers port from most US carriers in 7–10 business days. The operator keeps their published number; Torch routes inbound and outbound through it without interrupting service.
It gets the call close. The summary is a starting point, not a final record: the operator edits before saving to the project log, and the recording is always available behind the summary for verification.
Hire Sabina — she works inside Forge, at hiresabina.ai.
Or run Torch on its own — custom quoted.
Start with a short operational assessment of your business.