An API for every client's number
Your software texts from a client's business number, sends them notifications, and hears about every call and text the moment it happens. Your client works in the same conversations from the app.
One number, shared by people and software
To customers it's the business's number. Behind it, your client answers in the app and your software sends and listens through the API, in the same conversations.
Send from the number. Hear everything it does.
Your software can act as the business, and it never misses what happens on the number.
Your softwaretoThe number
- Texts from the client's numberCustomers see the business. Your client sees each one in the app, marked Sent by API, and can step in.
- Notifications to your clientsThey land on all their phones with your agency's name on them. Free, and they don't use a number.
- Contacts from your CRMNames show up on your client's calls and texts, and stay in step with your records.
The numbertoYour software
- Every textWhen one arrives, when your client sends one from the app, and when it's delivered or fails.
- Every callWhen one ends, with who answered and for how long, and the moment one is missed.
- Every voicemailWith a link to the recording.
- Opt-outsWhen someone texts STOP, so your software stops too.
- Chat from your clientsWhen a client writes to your agency in the app.
And you can read it all back: calls, texts, voicemail and contacts, for every client or just one.
Start with one job, then add the next
Most agencies start with one of these. Each takes a few requests, and the docs walk through every one.
Text back missed calls
When nobody picks up, the caller gets a text from the business within seconds.
- Step 1: A customer calls the business and nobody picks up.
- Step 2: Your software hears about it within seconds.
- Step 3: It texts them back from the business's number.
Uses Missed call webhook, Texts API
Read the guideAI texting with a person in the loop
Your agent holds the conversation and steps back the moment your client replies.
- Step 1: A customer texts the business.
- Step 2: Your agent reads the conversation and replies from the number.
- Step 3: When your client replies in the app, your agent steps back.
Uses Texts webhook, Texts API
Read the guideReach new leads first
A lead from a form, an ad or your CRM gets a text from the business right away.
- Step 1: Someone fills in a form on the client's website.
- Step 2: Your software texts them from the business and notifies your client.
- Step 3: Their reply reaches your client's phones.
Uses Texts API, Notifications API
Read the guideSend appointment reminders
Customers get a reminder from the business, and their replies reach your client.
- Step 1: Each morning, your software reads tomorrow's bookings.
- Step 2: Each customer gets a reminder from their business's number.
- Step 3: Replies land in your client's app and at your server.
Uses Texts API, Texts webhook
Read the guideLog every call and text in your CRM
Calls, texts and voicemails land on the customer's record as they happen.
- Step 1: A call ends, a text comes or goes, or a voicemail is left.
- Step 2: Your software gets each one as it happens.
- Step 3: It adds them to the customer's record.
Uses Call, text and voicemail webhooks
Read the guideKeep opt-outs in sync
When a customer texts STOP, your CRM stops too.
- Step 1: A customer texts STOP.
- Step 2: Texts to them from that business stop at once.
- Step 3: Your software hears it and updates your CRM.
Uses Opt-out webhook
Read the guide
Nothing lost, nothing sent twice
What makes it safe to hand a client's customers to your software.
- Keys that only do their job
- Limit a key to one client, chosen clients or a group, and to the actions it needs. Roll a key without downtime: the old one keeps working for up to 7 days.
- Webhooks you can check
- Each one is signed with your endpoint's secret, so your server can tell it came from AgencyPhone in the last 5 minutes.
- No double texts
- Give each send a name, like a booking and its reminder. Repeat it within 24 hours and you get the first result back instead of a second text.
- No missed events
- If your server doesn't answer, we try seven more times over about two days, and every attempt shows in your delivery log.
One event, when your server is down for a while
- First try
- +1 min
- +5 min
- +30 min
- +2 hr
- +6 hr
- +12 hr
- +24 hr
The details are in the docs
Every request, payload and webhook, with code you can copy. No code of your own? n8n, Make and Zapier can send every request and start a workflow from every webhook.

