What this package is
This combined package includes both:
Inbound calling (answer, qualify, capture, route)
Outbound calling (cold/warm outreach, qualify, capture, route)
It uses the same core providers and data destination as the individual packages, but delivered together as one connected system.
Provider options
VAPI
Retell
Default data destination
By default, this workflow uses Supabase as the primary database for storing call outcomes and captured lead details.
Best for
Businesses that need inbound coverage and outbound outreach
Teams that want one AI calling system to handle both directions
Companies replacing or reducing a human calling team
What’s included (baseline)
Inbound call workflow + qualification
Outbound call workflow + qualification
Lead detail capture (shared fields where possible)
Outcome routing (default: Supabase; can be CRM/ticketing via add-ons)
Basic validation/testing
Lead qualification criteria (you control this)
You define what counts as a lead and what counts as a non-lead for both inbound and outbound flows.
Workflows included (admin operations)
This package can include operational workflows such as:
Agent creation
Agent delete
Agent edit
Call monitoring (lead vs non-lead separation)
Number import/edit/integration workflows
Provider notes (limits, numbers, and setup complexity)
Concurrency (provider limits)
Providers have concurrent call limits based on your provider plan.
A common baseline is around 20 concurrent calls (plan dependent).
Concurrency can usually be increased by upgrading the provider plan (for example, incremental add-ons may be available).
Enterprise-level provider plans can remove practical concurrency limits (plan dependent).
Phone numbers (Twilio / SIP trunking / imports)
You can connect Twilio numbers and other numbers depending on provider support.
SIP trunking is an option for connecting numbers in some setups.
You can also use provider-managed numbers if your plan supports it.
Retell number import + call forwarding (important)
Retell’s call forwarding behavior can depend on how the number is imported:
If the number is imported using a “native provider” method, forwarding may be limited.
If the number is imported using a SIP-trunk-style method, forwarding flexibility is typically better.
VAPI vs Retell (high level)
VAPI: more powerful/flexible, but typically more complex to set up and may require more setup effort.
Retell: easier to set up, but number import and forwarding can be more finicky depending on the import method.
If you tell us your constraints (numbers, forwarding requirements, and target concurrency), we’ll recommend the best provider/setup.
Common add-ons
CRM integration
Email integration
Email follow-up automation
Calendar booking
After-hours rules
Routing/escalation
Frontend/dashboard UI (optional)
What we need from you
Business context + offer
Inbound call flow goals
Outbound outreach goals (cold/warm)
Qualification rules
Desired fields to capture
Numbers and forwarding requirements
Desired routing destination (Supabase/CRM/ticketing)