Avoma's Scheduler gives every paid plan unlimited 1:1 scheduling links, but the features a revenue team cares about are gated. Group, round-robin and embedded scheduling are included from Organization; on Startup they arrive only with the Lead Router add-on, which costs $19 per seat per month billed annually or $25 per seat per month billed monthly.[1] The same add-on carries the routing itself: HubSpot and Marketo form qualification, rules on CRM owners and custom fields, SDR-to-AE hand-offs and saving booking contacts to the CRM. Our verdict is simple. A team that already records its calls in Avoma can run inbound booking without a second scheduling vendor, as long as it buys router seats only for the reps who need them.

The Toolkit take
$19
Lead Router add-on per seat per month, billed annually ($25 per seat per month billed monthly).
Unlimited
1:1 scheduling links on every paid Avoma plan
7
Capabilities listed for the Lead Router add-on
2 form tools
Router forms: HubSpot and Marketo only

What every paid seat already schedules

Before any add-on, each recorder seat comes with unlimited 1:1 links, access to scheduling links across the team, custom event titles, and scheduling from the Chrome extension and the iOS and Android apps. Avoma's help center says paid users can create as many scheduling pages as they like, each offering several meeting lengths, and it describes the Scheduler as automating reminders, rescheduling and no-show handling. Reminder emails carry a reschedule link and reach every attendee on the invite, not just the organizer. Bookings sync both ways with Google Calendar and Outlook, and a page tied to a meeting purpose drops the matching note template into the meeting.

Scheduling feature Startup Organization Enterprise
1:1 scheduling links Unlimited Unlimited Unlimited
Team access to links, custom event titles Included Included Included
Chrome extension and mobile scheduling Included Included Included
Group and round-robin pages Lead Router add-on only Included Included
Embedding the scheduler on your website Lead Router add-on only Included Included
Routing rules, form router, SDR-to-AE hand-off Lead Router add-on Lead Router add-on Lead Router add-on

That table hides a real choice for small teams that only want round robin. Moving from Startup to Organization adds $10 per recorder seat per month at either billing term, and it moves every recorder, because all recording users must share one plan. A router seat costs $19 per seat per month billed annually. By our arithmetic, assuming each rep in a round-robin pool holds a router seat, Startup plus the add-on stays cheaper while fewer than about half the recorders need seats on annual billing, and fewer than 40% on monthly billing.

Take a 10-recorder team. With three reps in pools, Startup plus the add-on wins at both terms. With five, it wins only on annual billing. With six, Organization wins at both, and it also brings API access, webhooks and custom note templates. Avoma has no free recording plan, but its 14-day trial of Organization includes every add-on with no card, which is the cheapest way to build a router before paying; the full plan math is in our Avoma pricing guide.

Who needs a Lead Router seat, and what it carries

Avoma's help center is explicit on seats: anyone who manages lead routing or receives bookings from the router needs a Lead Router add-on seat.[2] Add-ons are assigned per user by admins under Settings, in the Billing and Members pages, and they follow the base plan's billing cycle, so an annual account cannot add a month-to-month router seat. Billed annually, a seat saves $72 a year against monthly billing ($228 versus $300 per seat a year, by our arithmetic). Avoma designs this routing for B2B sales teams, not consumer bookings. The pricing matrix lists seven capabilities behind the add-on:[1]

Curious how Avoma feels in practice?Try Avoma →

Building personal and team pages

Start with the calendar. Avoma needs a Google or Outlook calendar connected before it can show real availability, and the same connection drives recording, so one step covers both jobs. Do this for every rep who will appear on a team page; on group pages, Avoma sends final invites only to members whose calendar is connected. From there the work runs in a clear order:

  1. Create purpose-based 1:1 pages. Help recommends several pages for different meeting types; link each purpose to a note template so booked calls open with the right structure.
  2. Add a group page. Event length runs from 15 minutes to 6 hours. Members without a connected calendar get an email asking them to connect, and final invites go only to members whose calendar is connected. Only the organizer can edit the whole page.
  3. Add round-robin pages. Avoma's product page lists equal, availability-based and weighted distribution, daily caps per rep, and adjustments for cancellations and no-shows. Each page shows monthly distribution stats.
  4. Use managed pages for consistency. An admin builds a page template and assigns it to members; help says both the admin and those members must be on a paid plan.
  5. Install the sharing tools. The Avoma Scheduler extension comes from the Chrome Web Store and lists your schedules or creates new ones; the mobile apps share links from a Scheduler tab but cannot edit pages.
💡
Toolkit tip
Build segment pages before rules

The Lead Router does not create pages, so give each inbound segment its own round-robin page first. Rules run top to bottom, so put the narrowest segment on top.

Two refinements help inbound teams. Query parameters such as name, email, company, phone, role and purpose prefill the booking form. After confirmation, a page can redirect invitees to an external URL after three seconds, which suits a thank-you page with tracking. One snag affects Google users. Under Google Calendar's policy on unknown senders, a first-time invitee may need to confirm the event from the email before it lands on their calendar.

Wiring the router to your website forms

The router sits between a submitted form and a booking page. It does not create pages, so each inbound segment needs its own round-robin page before you write a single rule. Then connect the form: Avoma supports HubSpot and Marketo forms only, even when Salesforce is your CRM, and its product page says the fields come across automatically. Teams using Marketo landing pages rather than embedded Marketo forms need Avoma Support to add the router for them.

Rules come next. Order matters. Avoma evaluates them top to bottom and routes the lead on the first rule it matches, so put the narrowest segments first. Each rule takes only one CRM matching condition, but you can create several CRM-based rules, each checked in order. A rule can send the visitor to a one-on-one, round-robin, group or managed page, or to an external URL. Help recommends round-robin pages for inbound segments and managed pages for owner-based routing, where Avoma checks HubSpot, and Salesforce Account records for the domain rule.

Every router also needs a fallback for leads no rule catches: a custom message, an external URL, or a catch-all scheduling page. Avoma's product page says going live takes one embed snippet pasted on the page that hosts the form. Test each segment with a dummy submission before you publish, because a misordered rule quietly sends everyone to the first match.

⚠️
Watch out
Only HubSpot and Marketo forms route

The Lead Router reads HubSpot and Marketo forms only, even for Salesforce users; Marketo landing pages need Avoma Support to add the router.

Hand-offs, CRM write-back and reporting

For outbound teams, the Handoff Router lets an SDR book the right AE while the prospect is still on the call; Avoma's August 2024 update describes routing rules, custom hand-off forms and CRM updates, set up under Settings. After a booking, the router writes four fields to HubSpot and Salesforce: Booking Source, Booking Status (Booked or Abandoned), Meeting Creation Date and Meeting Outcome. Admins must create those custom fields first, with the exact names help gives.

💡
Toolkit tip
Create the four CRM fields first

Booking Source, Booking Status, Meeting Creation Date and Meeting Outcome must exist in HubSpot or Salesforce with Avoma's exact names before the router can write them.

Booking contacts reach the CRM through the add-on, and help says writing booker details from query parameters into a HubSpot Contact or Salesforce Lead property needs Support to set up. Scheduler Reports compare page views, completed bookings and booking rate per page, while Router Reports track assignments as they happen. On Organization and Enterprise, admins can also add webhooks under Settings, Organization, Developer for bookings, cancellations and reschedules. Our Avoma CRM integration guide covers the note sync that runs alongside.

⚠️
Watch out
Duplicate HubSpot meeting events

Avoma's help says turning on the router's meeting-engagement setting while reps also sync their calendars to HubSpot creates duplicate events, and the calendar-sync copy lacks Meeting Type and Outcome.

Ready to put Avoma to the test?Try Avoma →

Weighing it against Calendly and Chili Piper

Calendly is the familiar standalone choice. Calendly Teams costs $16 per seat per month billed annually or $20 per seat per month billed monthly. That plan bundles round robin, routing forms and Salesforce sync. Calendly also offers a free plan with one event type, and invitees need no seat. For a revenue team weighing the two, the difference is structure: Calendly Teams bundles round robin and routing forms, including Calendly and Pardot forms, in its seat, while Avoma sells routing as a separate per-seat add-on beside a recording plan, so its case rests on booked meetings flowing straight into recorded calls, notes and CRM activity in one system.

Chili Piper sits at the other end. Chili Piper Growth starts at $1,250 per month billed annually with 15 seats included and $45 per extra seat per month, and Scale starts at $3,500 per month with 30 seats.[3] Chili Piper bills annually only. Its standalone ChiliCal links cost $12 per user per month with a 200-seat minimum and no routing. Avoma's per-seat add-on suits teams too small for a 15-seat floor. Avoma's February 2026 customer story says HiHello replaced Chili Piper with Avoma for lead routing.

Frequently asked questions

Can I try the Lead Router before paying for it?+

Yes. Avoma's 14-day free trial is the Organization plan with all add-ons enabled and needs no credit card, so you can build pages and routing rules during it; afterwards the account becomes a viewer unless you buy seats.

How far ahead can invitees book through an Avoma scheduling page?+

Avoma's help center says invitees can book at most 6 months into the future on a scheduling link.

Can I restyle the embedded Avoma scheduler?+

Embeds come as inline or popup widgets, and Avoma's help center says custom CSS is not supported. Embedding is included from Organization, or on Startup through the Lead Router add-on.

Can I pay for Lead Router seats monthly on an annual Avoma plan?+

No. Add-ons follow the base plan's billing cycle, so an annual account buys router seats billed annually.

The bottom line

Avoma's Scheduler is worth setting up if your team already records its calls in Avoma. Unlimited 1:1 links come with every paid seat; group, round-robin and embedded pages start on Organization or arrive on Startup with the router add-on; and real routing always needs router seats for the reps who manage or receive it. Build the segment pages and CRM fields first, then the rules, then the fallback. Count seats before choosing a plan, since on annual billing the cheaper path flips once about half your recorders need router seats.

Sources
  1. [1] Avoma pricing plans (2026-11) https://www.avoma.com/pricing
  2. [2] How to configure inbound lead routing in Avoma Scheduler (2026-11) https://help.avoma.com/inbound-lead-routing
  3. [3] Chili Piper Pricing (2026-11) https://www.chilipiper.com/pricing