Skip to main content
Open Deploy → Testing to run and review real test calls. The page is labeled Call Testing after it opens.
Testing appears only when it is enabled for your team and your role has access to Implementation or Calls. If the page is missing, ask a team administrator or your Avoca implementation contact to confirm access.
Deploy → Testing captures calls placed from a registered phone number and keeps their feedback history. It is separate from Responder Simulation Testing, which runs repeatable, configured scenarios and assertions.

​
Register safe test caller numbers

Add each phone number that your team will use for test calls:
  1. Enter the valid 10-digit US phone number you will use to place test calls.
  2. Select Save.
  3. Use a registered number whenever you call the agent during testing.
Calls from registered numbers stay off the main Calls page and appear in this team’s All test calls history instead. You can register more than one tester’s number. To remove a number, select Unlink beside it. Historical test calls remain in Call Testing, but future calls from that number behave as regular calls: they appear on the main Calls page and can trigger ServiceTitan bookings.
Confirm that you are working in the intended Avoca team before registering or unlinking a number. Unlinking changes how future calls from that number are routed and recorded.

​
Choose whether test calls can book

Review Book real jobs from test calls before placing a booking test:
  • When it is on, bookings land in the connected CRM like real bookings. Say “test” at the end of each call so dispatchers can identify the record.
  • When it is off, Avoca skips bookings made from registered test numbers, so those test calls do not create CRM jobs.
The setting is available after at least one test number is registered and applies to the team’s registered test numbers. Changing the switch saves the new behavior immediately.
Turning on real bookings can create production CRM records. Use approved test data, verify the result, and cancel or clean up test records according to your CRM procedures. Never use a real customer’s information without authorization.

​
Complete the test scenarios

Call Testing presents each required scenario as a separate card. A card can show Not tested, Passed, Issues found, or Retest, and the page reports how many required scenarios have passed. For each scenario:
  1. Select the scenario card.
  2. Call the displayed agent number from a registered test number.
  3. Follow the displayed script and let the call reach the requested outcome.
  4. In Agent Feedback, select the test call you just placed. A newly completed call can be selected automatically when it is the clear match, but verify the call before submitting.
  5. Answer every required feedback question and select Submit feedback.
The required scenarios check:
  • An in-area booking for an existing customer
  • The resulting ServiceTitan booking for ServiceTitan teams
  • An out-of-area request
  • New-customer questions about services, fees, and memberships
Submitting feedback updates the scenario card. You can select Run again at any time. When feedback identifies an issue, Avoca automatically opens a support ticket associated with that test call. After every ticket on the issue call is resolved, the card changes to Retest until a later run passes. Completing feedback for every required scenario marks the corresponding Get Started testing step reviewed. The free-form scenario does not count toward that completion state.

​
Run free-form tests

Select Add test call to test a business-specific edge case after the required scenarios. The free-form guide suggests interruptions, changed requests, unexpected questions, and scenarios that have surprised your team before. Place one call, select its record, and submit one feedback entry. Repeat Add test call for every additional call so each result remains attached to the correct recording and transcript.

​
Find and organize test calls

All test calls is a newest-first history of calls from registered test numbers. Each row shows its status, linked scenario, date, time, duration, and feedback comment. Select a row or View call to open it, and use the page controls below the table for older results. A new call can remain in progress while its recording and transcript finish processing. A dash in the Test column means that no scenario feedback has been attached to that call yet.

​
Review a call

The call detail page can show:
  • Status, direction, date, duration, caller, and Avoca call ID
  • Recording, summary, and a transcript preview
  • The full Transcript tab
  • Feedback captured during the guided test
Use the recording and transcript together. In your feedback, describe what happened, what you expected instead, and the point in the call where the behavior diverged.

​
Get help with a test

When scenario feedback indicates that something went wrong, Avoca automatically opens a support ticket for that call. Use Go to Support to track it. For a problem outside the scenario feedback flow, select Open a ticket on Call Testing. You can also open a call and use its available flag action. Describe what happened, what you expected, and where the behavior diverged. Do not include passwords, API keys, payment data, or unrelated customer information.

​
If a test call is missing

Confirm all of the following:
  • You placed the call from the registered caller number.
  • You selected the correct Avoca team.
  • The call is not on another results page.
  • The call has had time to finish and process.
If the call still does not appear, record the time of the test, the caller number’s last four digits, and the agent number you dialed, then contact Avoca Support. Do not send a full recording or customer data through an unsecured channel.