Rides Your Rails, Not Ours
ABBY PORTAL · CALL SUMMARY
ANSWERED BY ABBY · 2:14 PMRosa Jimenez
(505) 555-0140 · 3 min · New caller
Asked about weekend service; message taken; callback number confirmed.
Message taken
Call notifications are sent through your SendGrid account, so they inherit your domain authentication and appear in your own activity feed and event data like anything else you send. Deliverability, logging, monitoring: the properties your team already trusts apply to your calls too.
It's deliberately one-way and deliberately boring: Abby answers the call, the notification goes out through your account, and your infrastructure decides what happens next.
Built To Be Parsed
Subjects and structure stay consistent call after call, so a filter, an inbound-parse handler, or a short script can pull out the caller, the reason, and the outcome without fragile pattern-matching. The format is confirmed at onboarding and then it doesn't move.
Where notifications go is entirely yours to decide: an ops inbox, a ticket-creating address, a distribution group, an internal tool. Anything that can receive email can receive your calls.
The Notification, Line By Line
| From the call | Where it lands in SendGrid |
|---|
| Caller name & number | Header block, first lines of the notification |
| New or known caller | Tag in the subject line |
| Reason for calling | Subject line + opening sentence |
| Outcome or promise made | Outcome line, under a consistent label |
| Call time & duration | Metadata footer |
| Callback number | Follow-up line |
The structure is set with you at onboarding and stays consistent call after call, so anything parsing these emails keeps working.
Where Teams Plug It In
Into the ops inbox your scripts watchNotifications land on an address your tooling already parses, so calls enter the same pipeline as everything else.
Alongside your transactional mailCall alerts ride the same authenticated domain as your receipts and system emails: one sending setup, one place to monitor it.
Into the event stream you already logDeliveries show up in your SendGrid activity and event data like any other send, so call notifications are observable, not a black box.
Feeding the internal tools you builtIf your dashboard or ticketing flow ingests email, calls appear in it next to everything else, with no new endpoint to stand up.
How It Works
1Onboarding connects your SendGrid account and confirms the sender, destination addresses, and notification format with you.
2Abby's receptionists answer your calls 24/7 per your instructions: screening, messages, and follow-up promises included.
3Each call becomes a structured notification sent through your SendGrid, landing wherever your infrastructure routes it.
FAQs
Why send notifications through my SendGrid instead of Abby's email?
They inherit your domain authentication and show up in your own activity and event data. Your answering service's notifications become part of the email infrastructure you already monitor.
Does Abby get access to our mail or our other sending?
No. Abby only sends call notifications through the connection set up at onboarding; it never reads mail and never touches your other traffic.
Can our systems parse the notifications automatically?
Yes. Subjects and structure are consistent and confirmed with you during onboarding, so filters and parse handlers keep working call after call.
Which AI receptionist works with SendGrid?
Abby: live virtual receptionists plus an AI receptionist option, and calls answered by either send through your SendGrid the same way.
Our stack runs on a different email provider. Can you support it?
Almost certainly. If your provider isn't in our catalog yet, we'll build the integration for you during onboarding at no charge.
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
