Replies by text
Customers text the business's number and the agent texts back. Short replies, one question at a time, drawn from the same knowledge base the phone agent uses.
Texting
Texts answered the way calls are.
A customer texts a business number and waits. The reply comes when somebody gets a minute, often the next day, and the photo they sent never gets looked at.
Text campaigns and the texting API run alongside the texting agent.
What the agent does
Short replies, one question at a time, from the same facts as the phone.
The same agent that answers the business line answers its texts, so a customer gets one answer whichever way they ask.
Reads a photo
A customer texts a photo of the error on their screen, the damaged delivery or the meter reading. The agent reads it and answers what it can see.
Hands over when asked
The moment somebody asks for a person, gets upset, or asks something the agent should not guess at, it stops. The whole thread is emailed and texted to the business and a lead is filed.
Text campaigns
An opening message, follow-ups to the people who did not reply, and a short conversation with each reply. Sends are spread across the business's numbers, and a refused text is retried from another.
Texting API
Plain texting for the client's own software: reminders, codes, dispatch notices. Replies are posted back to their software and opt-outs are handled by the platform. New Zealand and Australian numbers.
Its own number
A New Zealand mobile number for a New Zealand business, an Australian one for an Australian business, set up by the platform during onboarding, so two-way texting lands where it should.
Two things it does not do
- It cannot send a photo back.
- It does not book into a calendar or look up a CRM over text. The texting agent offers a call instead of guessing.
How it goes for the customer
A text in, an answer back, a person when it matters.
- The customer texts the business. Any hour, any day. There is no office to be closed.
- The agent replies. A short answer, one question at a time, from the same knowledge the phone agent uses. A photo gets read and answered.
- Somebody asks for a person. Or gets upset. The whole thread goes to the business by email and text, and a lead is filed.
- A campaign runs the other way. Opening message, follow-up to non-repliers, a short conversation with each reply. STOP ends it for good.
What the business gets
The whole thread, filed where the next person can find it.
Nothing lives only on a handset. Every handover arrives with its history attached.
- Every handover emailed and texted to the business with the whole thread, not just the last message.
- A lead filed in the leads list, with the text history for that number beside it.
- STOP honoured and counted, so the business can see how a campaign landed.
- Replies to API texts posted straight back to the client's own software, with opt-outs handled first.
- Results into anything else through Zapier, the REST API and webhooks.
Sold through partners
Texting sits beside the phone agent in your catalogue
Text campaigns pair naturally with outgoing calls: the agent rings, texts the people it misses, and carries on by text. You set the price; Talkgate runs the platform and the numbers. Offer the texting agent to the clients whose customers would rather text than ring; see the partner programme.
Works with
Plugs into the client's own software.
One API, one token with ticked abilities, with an OpenAPI spec for import. See all integrations.
Next step
See a text thread handed over, start to finish.
A partner briefing shows the texting agent, a campaign run and the API, and a thread handed to a person.