Skip to main content
Simple Scheduler gives customers a guided online booking experience. Open Products → Simple Scheduler in dashboard.avoca.ai.
Simple Scheduler and its settings appear only when the product is enabled and your role has access. Integration-specific tabs and fields appear only when they apply to your team.

​
Simple Scheduler pages

  • Overview: sessions, bookings, conversion, funnel progress, and customer journeys
  • Appearance: colors, logo, footer, and privacy link
  • General Settings: scheduler wording and core booking behavior
  • Service Types: services customers can select
  • Questions: information collected before scheduling
  • Post-Booking Questions: optional information collected after a booking
  • Ownership: homeowner or property-ownership verification
  • Compliance: consent, disclaimer, privacy, and terms content
  • Tags: CRM tag behavior when supported
  • Links: shareable links, UTM mappings, and embed instructions
  • API Keys: website widget keys and allowed domains
  • RwG: Reserve with Google setup when enabled
  • Follow-up Statuses: a limited, feature-gated catalog for drop-off follow-up when enabled; Avoca manages the status definitions

​
Read the Overview page

  1. Select one scheduler or all schedulers.
  2. Choose a date range.
  3. Review Sessions, Bookings, Conversion Rate, and Average Booking Time.
  4. Use the funnel to see where customers stop between opening the scheduler and booking.
  5. Filter journeys by booking status and traffic source.
  6. Review UTM performance to compare tracked sources, mediums, and campaigns.
  7. Export a CSV when you need to analyze the underlying journeys outside Avoca.
A session without a booking is a drop-off, but it does not always indicate a technical problem. Compare the funnel step, customer journey, requested service, and available booking windows before deciding what to change.

​
Review a session’s booking path

Select a customer-journey row to open Session Details when a session ID is available. The panel shows the recorded booking steps in chronological order. Depending on how far the customer progressed, it can include:
  • Account Lookup: whether Avoca matched an existing customer and location, plus whether the customer used an existing match, edited or rejected a match, or entered the address manually
  • Job Type Classification and Business Unit Resolution: the selected value and the recorded reasoning
  • Availability Fetch: the scheduling method; the resolved job type, business unit, service type, appointment type, and residence type when recorded; and the availability windows returned
  • Customer Selection: the requested appointment or selected date and time, arrival window when available, and submitted notes
  • Booking Outcome: whether the CRM booking succeeded and its job ID
Each recorded step shows a success, warning, error, or skipped status, its timestamp, its duration when available, and any recorded error. A linked Booking Request summary shows the final request status and, for ServiceTitan bookings, can link directly to the job. Expand the availability summary to inspect windows grouped by day, including their time range, named window, and fee when recorded. The panel initially shows three days; select Show more days when the trace contains additional dates. When Availabilities found includes a second number marked before filtering, the CRM returned that many raw slots but lead-time, cutoff, capacity, or overbook-cap rules removed some or all of them. If no before-filter number appears, start by checking the CRM’s returned capacity and the resolved job type and business unit. This distinction helps separate a source-capacity issue from an Avoca filtering or configuration issue. If the panel says No details were recorded for this session, use the journey row and CRM record for the available evidence. Sessions created before this trace was recorded may not have a step-by-step history.
  1. Configure the booking experience in the order described in Configure Simple Scheduler.
  2. Test every service path on desktop and mobile.
  3. Publish the generated link or widget only after a successful test booking.
  4. Review drop-off and conversion weekly.
  5. Change one major part of the flow at a time, then compare the same date window.
Use Install and launch Simple Scheduler for the production widget, domain, notification, and launch checklist.