A trigger built on real conversationsEvery call your receptionists answer produces a complete record (caller, reason, summary, outcome) ready to start a scenario.
Anywhere Make connectsMap call details into your CRM, a database, a message, a sheet: any app Make reaches, in any shape your modules define.
Yours to build and rebuildSelf-serve by design. You own the scenario, the filters, and the logic; change a branch at midnight without asking anyone.
One Bundle In, Your Modules Take Over
ABBY PORTAL · CALL SUMMARY
ANSWERED BY ABBY · 7:58 AMLeah Okafor
(313) 555-0141 · 3 min · New caller
Water heater leaking into the garage; needs someone today; address and gate code captured.
UrgentNew caller
MAKE · SCENARIO RUN
⚡Trigger · Abby · new call record
↓
🔀Router · Reason mentions "leak" → urgent branch
↓
🛠️Module · Field app · create job for Leah Okafor
↓
💬Module · Text the on-call tech with the summary
A new caller, Leah, reports a water heater leaking into her garage. Abby's receptionist answers, captures the address and the urgency, and the finished call record arrives in your scenario as a fresh bundle. Your router checks the reason, the urgent branch fires: a job is created in your field app and the on-call tech gets a text with the summary.
You drew that logic; Abby just keeps it fed. Every answered call arrives the same shape (caller, reason, summary, outcome) so your filters and routes behave the same at 8 AM and 2 AM.
You Draw The Scenario, Abby Feeds It
Everything in our catalog is a native integration we set up for you at onboarding; you should never need an automation platform for the basics. Make is for the builders: the visual canvas where you decide every branch, filter, and destination. Abby's part ends at delivering a complete, consistent call record; yours begins at the first module.
Data moves one direction: out of Abby, into your scenarios. Nothing you build reaches back to change how calls are answered; when you want handling changed, you tell your receptionist team, not a workflow. That boundary keeps your phones predictable no matter what you're experimenting with on the canvas.
Five Branches Off One Phone Call
The reason mentions an active job→The record lands in your project tool, matched to the job, with the summary attached.
It's a new caller during business hours→Your CRM gets a lead and the owner gets a message before the follow-up window cools.
The call comes in after hours→The record waits in an aggregator and arrives as one morning digest, not six midnight pings.
The caller is on your VIP list→A text goes straight to your phone with the caller's ask, moments after the call ends.
Nothing matches→The fallback branch files the record in your call-log base; every call lands somewhere, by design.
Four Scenarios, One Trigger
The niche tool we haven't metYour industry app isn't in our catalog yet? One scenario maps call records into it today, and if it matters enough, ask us to build it native.
A ping when it's urgentFilter on the reason or the caller, then message yourself: the leak, the VIP, the cancellation reaches your pocket in moments.
After-hours, batched for morningEvening call records collect in your scenario and arrive as one tidy morning summary, formatted the way you like it.
One call, several destinationsA single record fans out (the CRM gets the lead, the sheet gets the row, the team chat gets the heads-up) in one scenario run.
How It Works
1Your onboarding team connects Abby to your Make account with you and confirms call records are arriving.
2Abby's receptionists answer 24/7 as your business; each call ends as a structured record: caller, reason, summary, outcome.
3Your scenarios take it from there: filter, route, and map the details anywhere Make connects.
FAQs
Can Abby's answering service trigger Make scenarios?
Yes, that's the integration. Every call Abby's receptionists answer produces a structured record that can start your Make scenarios, with the details mapped wherever your modules send them.
Is Make the same as Integromat?
Yes, Make is the platform formerly known as Integromat. If your scenarios date back to Integromat days, they'll treat Abby call records like any other incoming data.
Can a scenario change how Abby answers my calls?
No. Data flows one way, out of Abby. Call handling (greeting, screening, transfer rules) changes with your receptionist team, so an experiment on the canvas can never break your phones.
Do I need Make for the integrations in your catalog?
No. Catalog integrations are native and built for you during onboarding at no charge. Make is for what's beyond the catalog, and for people who like owning the logic.
What's in the call record a scenario receives?
Caller name and number, new-versus-known status, the reason in one sentence, a summary of the conversation, the outcome, and timestamps. Records look the same whether a human receptionist or Abby's AI receptionist answered.
Use a tool we haven’t listed?
We build missing integrations for new customers during onboarding, free. Tell us what you run on and we’ll connect it.
Schedule a CallCall 877-303-5757
