Phone.inc for MakeComing soon
Every call, on the canvas.
You build your automations visually because you want to see how the work flows. Phone.inc puts the phone on that canvas: one trigger module, and the rest of the scenario is yours.
Event sent
call.missed
- from
- +45 22 90 41 07
- at
- 12:05
- attempts
- 2 today
Your automation · running- Search Records in HubSpot
- Create a Task for the owner
- Send a message in Slack
Task created: return Mette's call
What it does
Your phone on the canvas. One trigger module, every scenario.
Make is good at the messy middle: look this up, check that, branch if it matters, then act. Phone calls are exactly that kind of messy, and until now they never reached the canvas at all.
- Every call becomes a bundle
- Calls, missed calls, voicemails, and texts arrive as an instant trigger with the caller, the timing, and the transcript.
- Search before you act
- Look the caller up in your CRM, your accounting, or your own database, then branch on what you find.
- Modules for the phone side
- Send a text, add a contact, or change your opening hours from the same scenario. The phone is an app like any other.
- Voicemails with the transcript
- The transcript arrives in the bundle, so a scenario can read what was said and route on it, not just on the number.
- One scenario, every number
- Run one scenario across every number and person in your account, and let filters decide what deserves attention.
- No code, when it opens
- You will find Phone.inc in Make's app directory and connect it like any other app. Nothing to host, nothing to maintain.
In the product
One minute after Mette. From missed call to task assigned.
12:05:00
Missed call
Nobody picks up
Mette rings while you are on a roof, in a van, or with a customer. The phone rings out. This is the moment small businesses lose work, and it is the moment nothing usually happens.
- Second attempt today
- Rang out, no voicemail
- Number recognised
Mette Holm
Incoming · Main number
12:06:00
After the call
Phone.inc notices
The missed call is logged, matched to a number you know, and marked as the second attempt today. Then Phone.inc fires call.missed.
- Logged, not lost
- Attempts counted
- Event fired straight away
Mette Holm
Call ended · 0:24 unanswered
- Logged the missed call
- Matched it to a known number
- Noted it was the second attempt
- Fired call.missed
12:06:04
Your scenario
Your scenario runs
Make picks it up and does what you would have done: finds her in the CRM, creates a task for whoever owns her, and drops a line in the channel. She gets a call back today.
- Instant trigger, not polling
- Searches before it acts
- Runs every single time
Event sent
call.missed
- from
- +45 22 90 41 07
- at
- 12:05
- attempts
- 2 today
Your automation · running- Search Records in HubSpot
- Create a Task for the owner
- Send a message in Slack
Task created: return Mette's call
Your stack
Your tools, one phone. Connect as many as you run.
Integrations aren't either-or. Connect Shopify for orders, Dinero for invoices, and anything else you use. Each one takes about two minutes, and every call reads them all.
Make + Phone.inc
Put the phone on the canvas.
Join the waitlist. You get a free business number when your batch opens, and we will email you the day the Make app goes live.