AI Receptionist & Phone Answering

7 Test Scenarios to Run Before You Forward Your Main Number to Tinylawn

Use these seven Tinylawn test-call scenarios to check services, scheduling, lead capture, notifications, and call records before forwarding.

Tinylawn Editorial · Field service operations research ·
7 Test Scenarios to Run Before You Forward Your Main Number to Tinylawn
Table of Contents

Before you forward your main number to Tinylawn, run a deliberate set of test calls. A quick “Hello, can you hear me?” only proves that the number connects. It does not prove that the receptionist can explain your services, use the right business hours, offer a sensible appointment, capture a property address, or notify the right person afterward.

The seven Tinylawn test-call scenarios below cover the moments most likely to affect a real customer. You do not need to make seven separate calls. Combine related scenarios into a few realistic conversations so you can test more of the workflow without using unnecessary trial calls.


Prepare the account before testing calls

A test is only useful when the underlying settings are ready. Otherwise, you are measuring missing setup instead of the experience you plan to launch.

Review these areas first:

  • Business profile: Confirm the business name, address, service area, contact information, and time zone.
  • Services: Make sure every active service has a clear name and description. If the receptionist should discuss pricing, confirm the price and whether it should be presented as an exact amount or “starting at” price.
  • Business hours: Check each open day, the opening and closing time, and the earliest appointment availability.
  • Greeting and FAQs: Read the greeting aloud. Add answers for the questions customers ask often but that are not covered by the normal service information.
  • Notifications: Add the owner, office, or dispatch contacts who should receive email or text updates after calls.

Call your Tinylawn number from a phone that is not associated with the business account. The number is available in the Getting Started area and under Settings > Receptionist.

Keep a simple test sheet with four columns: scenario, what you said, what the receptionist did, and what appeared after the call. That record makes it easier to fix settings and repeat only the failed part.

1. Test the greeting and business identity

Start like a normal first-time caller:

“Hi, is this Green Street Lawn Care? What areas do you serve?”

Listen for the exact business name, a natural greeting, and a useful answer based on the profile you configured. Then introduce a minor misunderstanding. Use an old business name, ask whether you serve a town just outside your normal area, or refer to the wrong kind of company.

The goal is not to trick the receptionist. It is to hear how it handles uncertainty without inventing an answer. If the greeting sounds awkward or the service-area answer lacks detail, update the business profile or FAQ rather than hoping the phrasing improves on its own.

After hanging up, confirm that the call appears in the call list and that its summary matches what you actually asked.

2. Ask about a service and its price

Choose one common service and one service you do not offer.

For example:

“How much do you charge for weekly mowing on a half-acre lot? Do you also remove trees?”

The answer should reflect the active services in your account. If pricing is enabled, listen for the amount and whether it is described as a starting price. If pricing is hidden, the receptionist should not read it as though it were a public rate.

This test often exposes service descriptions that make sense internally but are unclear to a homeowner. “Turf maintenance” may need to become “weekly mowing, trimming, edging, and cleanup.” A seasonal service may need to be deactivated so it is not offered in the wrong month.

Check the transcript after the call. It should show what the caller asked and how the receptionist represented the service. Adjust the service record, then repeat this portion if the answer was incomplete or misleading.

3. Check business hours and a custom FAQ

Ask one question the business profile should answer and one that depends on a custom FAQ:

“Are you open Saturday? Also, do I need to be home for the estimate?”

This verifies two different sources of information. The hours should match the schedule and time zone in the account. The second answer should match the policy you wrote, not a generic assumption.

Good FAQ tests use policies where an incorrect answer would create friction later:

  • Whether customers must be home
  • Whether crews work in light rain
  • Whether the company hauls away clippings
  • How pets and locked gates should be handled
  • Whether the business carries insurance
  • When payment is due

If a policy has exceptions, write the FAQ so the receptionist can set a safe expectation without overpromising. “Our estimator can usually visit without you home if the property is accessible” is more useful than an unconditional yes.

4. Request an appointment at an available time

Now test the scheduling path with a time that should be open.

Give a real-looking name, phone number, service request, and property address. Ask for a specific day and time within business hours. The receptionist should check current availability before confirming anything.

After the call, inspect three places:

  1. The call record for its summary, transcript, and recording
  2. The Calendar for the scheduled appointment
  3. The Leads area for the captured customer and property details

Also confirm that the expected email or SMS notification reached the right team member. A successful spoken conversation is not a complete scheduling test if the appointment never reaches the working calendar.

Delete or clearly label the test appointment afterward so it cannot be mistaken for a real job.

5. Request a time that is not available

Make the next request intentionally difficult. Ask for a time outside business hours, a time already occupied, a past date, or a slot earlier than the minimum availability you configured.

Tinylawn should avoid booking the unavailable time and offer up to three alternatives. Listen for whether those choices are practical. If the options seem unexpectedly late or fall on the wrong day, inspect:

  • Business hours
  • Existing appointments
  • Earliest availability
  • Account time zone

This test is especially important for an owner who blocks production time, estimate windows, or personal appointments on the same calendar. The receptionist can only work from the availability it sees.

Do not leave the test after the first alternative. Accept one option and confirm that the resulting appointment lands in the correct calendar slot.

6. Reschedule and cancel an appointment

A receptionist is not only for new leads. Existing customers call when the original time no longer works.

Use the test appointment from scenario four or five. Call back, identify the appointment, and ask to move it. Confirm the new slot appears correctly. Then make another test request to cancel it.

Review the call category after each action. Tinylawn distinguishes between Appointment Scheduled, Appointment Rescheduled, and Appointment Cancelled. The Calendar should reflect the same outcome.

This scenario also shows whether a caller can provide enough information to identify the right appointment. If the test becomes confusing, check the transcript before changing settings. The caller may need to give the same name or phone number used during the original booking.

7. Submit a realistic quote request

Finish with the most important path for many lawn and landscape companies: a new property owner asking for an estimate without choosing an appointment.

Use a complete but clearly fictional test identity. Provide:

  • Name and callback number
  • Property address
  • Requested service
  • Preferred timing
  • One useful detail, such as lot size, gate access, slope, drainage issue, or current lawn condition

The receptionist should capture enough information to create a quote-request lead. Afterward, verify the lead record instead of stopping at the call summary.

Tinylawn may create or match the client and property, validate the address, attach the call, and add available property context such as parcel boundaries, lot details, or imagery. If the address cannot be resolved, the customer may receive a text asking for a correction. The lead should also preserve the service and desired timing gathered during the conversation.

This is the test that tells you whether the morning lead queue will be useful to an estimator. Ask: could someone open this record and know what the caller wants, where the property is, and what to do next?

Review the result after every Tinylawn test call

Do not judge the system only by what you heard on the phone. Each call produces an operational record.

Review:

  • The call category
  • The summary
  • The full transcript
  • The recording
  • Any related lead
  • Any related calendar event
  • Email and SMS notifications

Tinylawn can classify calls as General Question, Quote Request, Appointment Scheduled, Appointment Rescheduled, Appointment Cancelled, Needs Follow Up, or Spam. Those labels determine what your team sees next. A call can sound reasonable yet still need manual follow-up if the receptionist did not gather enough information for a complete lead.

If a test fails, change one setting at a time and rerun the shortest conversation that proves the fix. Editing services, hours, FAQs, and notifications all at once makes it harder to know which change mattered.

Choose a cautious forwarding mode for launch

Once the tests pass, decide when calls should reach Tinylawn. Keeping your existing business number means callers do not need to learn a new one. Your carrier forwards calls behind the scenes.

The common options are:

  • All calls: Every incoming call forwards immediately.
  • When busy: Tinylawn handles overflow while your line is occupied.
  • When unanswered: Tinylawn answers calls your team does not pick up.
  • When unreachable: Calls forward when the phone is off, out of service, or outside coverage.

Carrier support varies, especially for conditional modes. Confirm the setting with your carrier and place another test call after forwarding is active.

If you want a gradual launch, start with unanswered calls. Let the phone ring normally, allow Tinylawn to take what the team misses, and review those records for several days. Move to wider coverage when the results match your process.

Launch when the workflow works, not just the voice

The best test is not whether the receptionist sounds polished in one easy conversation. It is whether the business receives an accurate record, the customer gets a reasonable next step, and the team knows what to do after the call.

Run the seven scenarios, correct the underlying settings, and retest the weak paths. Then forward the main number with a clear review routine for the first week.

If you want to hear the workflow before changing your phone setup, book a Tinylawn demo.