Surfaces
iMessage and SMS
The messaging surface gives an agent a phone number people can text, and the agent answers in the same chat. Adapt sends and receives texts through Linq.
Each one-to-one chat with the number is one conversation with the agent. A text becomes an ordinary run with the agent's model, tools, and limits, and the final answer goes back as a text from the number. Group chats are ignored, since there's no way to address the agent in one.
Add a number to an agent
You need a Linq account and a number on it; Linq's free sandbox number works for trying it out. Only owners and admins can add a surface. Go to Agents, open the agent, then Settings → Where it answers → Add surface → Linq.
Setup asks for:
- Phone number: the full Linq number people will text, such as
+12025551234, from Phone Numbers in Linq. - API token: from API → Overview → Generate new token in Linq. Linq shows it once.
- Signing secret: in Linq, open Webhooks and create one with the connection's Webhook URL,
<your Adapt URL>/api/surfaces/<connection ID>, subscribed tomessage.received. Linq shows the webhook's signing secret once; it starts withwhsec_.
The Webhook URL must be a public HTTPS address; see Self-host.
Verify your phone
Texts start runs only from a member's verified phone, because a phone number alone vouches for no one. The last step of Linq setup verifies yours:
- Enter your phone number and choose Get a code. Adapt shows a code such as
ADAPT-7KQ2, valid for 10 minutes. - Text the code to the agent's number from that phone.
- The text proves you have the phone, so Adapt links it to your account. If another member had linked that number before, it moves to you.
A text carrying a code never starts a run. Remove unlinks your phone.
In this version the verification form appears only in Linq setup, which only admins can open. Other members' texts start runs only if the automation allows non-workspace members (below).
People are identified by the phone number they text from. Someone using iMessage from an Apple ID email address instead of a number can't verify.
Check the connection
Open the agent's Linq row under Where it answers to see its Setup check. Adapt checks the number and API token against Linq, and Texts passes once Linq has delivered a text. To confirm, text the number from your verified phone. A connection that's on is permitted to run, not verified healthy.
Who the agent answers
Each messaging surface comes with an automation, Respond to text messages, on the agent's Automations tab. By default it answers only members texting from their verified phone, and the run acts as that member, with their role and access.
Turning on Allow responses to non-workspace members for its event lets anyone who texts the number get an answer. Those runs are anonymous: no Adapt user and no workspace role. History search and Adapt administration tools are never available in text threads.
Texts and files
The agent is told it's texting, so it keeps answers short. Bold and italic show as styled text; headings, tables, and code blocks don't. A failed or interrupted run sends a short error instead of an answer.
- Text out: up to 10,000 characters per message.
- Files in: photos and other media in a text become the run's files, and a text with only media still starts a run. A file that can't be fetched, or is past the upload limit, becomes a note.
- Files out: up to 10 files and 25 MB per answer, sent with the text as one message. If Linq won't take a file, the answer goes without it and names it. If Linq refuses the message with its files, the text goes alone, naming them.
If Linq refuses a text, the delivery is marked failed. Any other error after the send started marks it uncertain, and it's never resent, so nobody gets the same text twice.
Read text threads in Adapt
The member who started a text conversation sees it in their chat sidebar. Any member who can view the agent can open a text conversation in Adapt, read-only, with each message labeled by its author or as anonymous. To continue it, text the number. The thread's owner and admins can rename or delete it; the next text in that chat then starts a fresh conversation.