Your Twilio number can send calls to GreetKeeper today
Forwarding works. A number you own in Twilio can ring GreetKeeper instead of your app. What GreetKeeper does not do is write anything back into Twilio.
Caller
“Your app kept telling me to leave a message. I need someone to look at my account before Friday. Can a person call me back?”
What happened next
- Caller's name, number and account reference captured in the transcript
- Summary sent to your support inbox two minutes after the caller hung up
- Webhook fired to your own endpoint with the same call data as JSON
How GreetKeeper connects to Twilio
Three states, and we publish the one that is true rather than the one that reads best.
| Tool | How it connects | What that means |
|---|---|---|
| Twilio | Not yet |
What Twilio is in this setup
Twilio is a developer platform for phone numbers, calls and messages. You buy a number, then write code that decides what happens when it rings. Nothing happens by default.
Every Twilio number has a voice configuration. When the number rings, Twilio sends a request to whatever you put there, and it plays back the instructions it gets. Those instructions are TwiML, Twilio's own XML format.
That is the hook you use. A TwiML response containing a Dial verb sends the call on to another number. Point that at the number GreetKeeper gives you and your Twilio line is answered by GreetKeeper.
Where the call record lands
Twilio keeps its own call logs, and GreetKeeper does not add to them. Here is what you actually get instead.
The call lives in GreetKeeper. You get the full transcript, a short summary of what the caller wanted, and their number. Your Twilio console will show a call was forwarded, with duration and cost, and nothing about what was said.
Email is the default delivery. You nominate the address during setup, and each finished call arrives there. Developers on Twilio usually want the webhook instead, so GreetKeeper posts the same record as JSON to any URL you own.
If the caller wanted an appointment, GreetKeeper books it into a connected Google Calendar or Outlook. That write is real. The Twilio side of your stack stays untouched.
Forwarding a Twilio number
Two ways, depending on whether you like clicking or writing code. Both take a few minutes.
Get your GreetKeeper forwarding number
GreetKeeper gives you a number when you set up your receptionist. Copy it. Everything below points a Twilio number at it.
Open the number in the Twilio console
Go to Phone Numbers, then Manage, then Active Numbers, and click the number you want answered. You'll see the Voice Configuration section.
Send the call to GreetKeeper
The quickest route is a TwiML Bin. Create one with a Dial verb pointing at your GreetKeeper number, then set the number's incoming call handler to that bin. If you already run your own webhook, return the same Dial verb from your code.
Ring the number and listen
Call it from your mobile. GreetKeeper should answer. Talk through a real scenario, hang up, then check both the transcript and your webhook payload before you move production traffic.
What this connection does not do
Questions about Twilio and GreetKeeper
Do I need to change my application code?
Only if your number is already handled by your own webhook. A TwiML Bin needs no code at all. If you have a webhook, return a Dial verb pointing at the GreetKeeper number.
Can I forward only after hours?
Yes, but the logic is yours. Your webhook can check the time and return a Dial to GreetKeeper outside your opening hours, and your normal flow inside them.
Will GreetKeeper show up in my Twilio call logs?
You'll see the forwarded leg, with its duration and cost. The transcript and the summary live in GreetKeeper, not in Twilio.
Point a test number at it first
Buy a spare Twilio number and try it. Two minutes, no card.