Report

Gets the whole problem down on the first call, and leaves it ready to fix.

The problem gets explained three times

Someone calling with a problem explains all of it, and then explains it again when someone finally calls back.

Service calls come in at the worst time: the customer is stressed, whoever answers is busy, and what gets written down is half a line on a notepad. The details the tech needs are missing, so someone has to call back to ask. Meanwhile no one knows if the job is open, who has it or since when.

Lea, Opslyn's AI receptionistLea · Summit Air's AI receptionistIncoming call · Friday 10:30 PM

My furnace makes a loud bang every time it starts up.

I'll write that up. When did it start, and is the house still warming up?

Tonight. It still heats, but it's loud.

Thanks. I've opened a ticket and texted you a link to send a short video of the sound.

Ticket #1048 created

Job ticket #1048

IssueFurnace bangs on startup · still heats
UrgencyMedium
PhotosVideo requested

It takes down the whole problem

Taking a service request isn't writing down a complaint. It's getting what the tech needs without calling back.

  • It asks what happened, where and since when.
  • It asks for the missing detail before the call ends.
  • It recognizes what's urgent, using your rules, and marks it.
  • It opens the job in the system your team already uses.
  • It tells the customer what was recorded and the ticket number.
  • It takes a 3 AM call the same way as a 3 PM one.

What to ask, and who to tell

Every shop has its own intake questions and its own idea of urgent. You write them down once.

The questions

The details you always need to act without calling back.

The job types

Which problems come in, and which are truly urgent.

Where it goes

The CRM, job board or inbox where tickets are opened.

The alert

Who gets told right away, and who can see it in the morning.

A job ticket, not a sticky note

By the time they hang up, there's a record with everything in it and the right person knows. No one has to piece the call back together.

  • The problem recorded: what, where and since when.
  • The caller's contact details, so no one has to chase them.
  • The urgency marked, so serious jobs don't wait their turn.
  • An alert to whoever handles it, the moment it comes in.
  • A history of what breaks most, which shows you patterns.

When the call brings a problem

Report steps in when a call isn't a question or a sale, but something that needs fixing.

After-hours calls

It takes the night call down in the same detail as the midday one.

Calls and texts in one place

It takes the request however it comes in, with photos if they text them.

After the job

It records callbacks and warranty issues and puts them in someone's hands.

Where the limits are

We'd rather you read it here than find out on a demo. Report writes it down and alerts; fixing it is still for people.

  • It doesn't fix the problem. It documents it and hands it to whoever does.
  • It doesn't judge urgency on its own. It uses your rules.
  • It doesn't promise arrival times. It only gives the ones you've set.
  • It's not 911. If there's real danger, it tells the caller to call 911 and alerts your on-call person.
  • It doesn't follow up on its own. Callbacks are your team's or your automations'.

What everybody asks

Five questions from anyone who takes problems over the phone every day.

See all FAQs ›

What your team needs to act without calling back: what's wrong, where, since when, how urgent, and who's calling, with contact details. If something's missing, it asks before hanging up.

Try it with your next service call

Tell us what to ask, and the next service request comes in complete.