Reach your customers where they already are: text. Tech Ringer AI sends and receives SMS via Twilio with full opt-in compliance, PII redaction, and capability-gated actions.
Four steps. Defaults are conservative — you can broaden later.
Bring your existing Twilio number, or provision a new one through the Tech Ringer AI dashboard. We handle the webhook configuration end-to-end.
Set the keywords that constitute opt-in and opt-out (HELP, STOP, START) and the compliance text that goes out with the first message. Required by US carrier rules.
Capability gating decides what the SMS agent can do — answer questions, look up account info, take actions. Defaults are conservative.
Send a test SMS to your Twilio number. The agent replies via SMS, the conversation lands in your audit log.
User: "What's my balance?"The agent looks up the account (read-only capability), responds with the balance, and logs the interaction. The phone number is stored, not the body of the SMS — PII redaction on tool results applies before any LLM provider sees the content.
SMS is the lowest-common-denominator messaging channel: works on every phone, no app required, deliverable to anyone with a number. That ubiquity comes with constraints — strict carrier rules about opt-in and opt-out, per-segment cost, no rich formatting. We built the SMS integration to handle those constraints automatically.
Opt-in compliance is the hard part. Every new conversation requires explicit opt-in, every message includes the required STOP/HELP keywords on first contact, and every opt-out is honored immediately and logged. The audit trail of compliance is the audit log — when a regulator asks, you have the receipts.
PII handling matters especially here. Phone numbers are themselves PII, and SMS bodies frequently contain identifiers (order numbers, addresses, account references). The tool-result safety pipeline redacts PII in any tool result the agent uses to compose a response — so the response itself can mention 'your account' without ever putting the account number in the LLM's context.
Currently US-focused, with international expansion in progress. Twilio's international SMS coverage applies — check the changelog for the current country list. International support requires per-country opt-in flow configuration.
SMS-only for now. MMS support is on the roadmap. For rich-formatted messaging, WhatsApp Business or in-app chat are better fits — both support media and formatting natively.
No. We don't train models on customer conversations — across every plan, every audience, every chat platform. PII is also redacted before any third-party LLM provider sees a tool result.
Yes. Input guardrails, URL safety scanning, PII redaction, capability gating, and audit logs run identically here as in the dashboard and on every other integration. Adding a chat platform doesn't expand your security surface area meaningfully.
Disconnect the integration from the dashboard at any time. That revokes the OAuth grant (or removes the bot from the platform, for non-OAuth platforms), all in-flight agent sessions stop, and any future invocations from that platform fail closed. The audit log of past activity stays accessible.
Free to start. $5 in credits on us. No credit card required.