01
Missed call caught
Unanswered and after-hours calls go to Catchline before they become voicemail.

Catchline by Mac Digital

Missed call caught. Job qualified. Appointment booked or escalated. Owner notified before the lead cools off.
Missed calls get answered
Jobs get qualified before callback
Bookings and emergencies get routed
Built for contractors and service businesses
Catchline is a managed answering layer for the business you already run. It does not force a new field-service platform. It catches the missed moment, asks the right questions, books what it can, and escalates what needs a human.

01
Unanswered and after-hours calls go to Catchline before they become voicemail.
02
The AI receptionist collects the caller, service, address, urgency, and job details.
03
Normal work gets booked into the calendar. Urgent calls are routed to the owner.
04
The business gets the summary, transcript, next step, and ROI record after the call.
Compliance is not optional
Your callers always know they're talking to an AI, and recording is always disclosed. The business profile can tune what the agent knows, but disclosure is not a setting clients can turn off.
SMS is transactional only. Pricing is never invented. Emergencies are escalated instead of being left as normal callbacks. Memories are tenant-scoped and shaped for per-contact erasure.

Interface preview
Owners get the record that matters: who called, what they needed, whether it booked, what changed in memory, and what the lead was worth.
Today
New service lead
Bookable job request
Memory: Follow-up preference captured
Emergency call
Configured urgent keyword
Memory: Owner handoff required
Vendor call
Sales pitch
Memory: Digest only
--
Calls caught
Counted from completed voice conversations.
--
Jobs booked
Written after calendar confirmation.
--
Revenue saved
Estimated from tenant pricing rules, never invented by the agent.
--
Response time
Compared against a voicemail baseline in the ROI report.
Owner summary template
Business name: caller requested a bookable service. Slot booked after calendar confirmation. Transcript and memory updates are linked in the dashboard.
Under the hood
The foundation keeps Retell, Twilio, calendar, LLM, billing, and memory behind provider interfaces so the business logic can move without rewriting the product.
Next.js app, AWS runtime target, typed env, CI checks, and operator-first onboarding paths.
Businesses, contacts, conversations, jobs, usage, notifications, memories, and calendar connections.
Every tenant table is scoped by a business_id claim with platform-admin policies separated.
Retell, Twilio, Google Calendar, Anthropic, Stripe, and memory sit behind typed provider interfaces.
AWS ECS/RDS/S3/SQS shape, ca-central-1 oriented data plane, and provider modules under /src/lib/providers.
AI disclosure, recording notice, transactional SMS only, erasure-ready data shape.
For Durham Region and GTA service businesses