Lesson 7 of 7 · 7 min

Routing directory and ad leads into one inbox

Route leads from directories and ads into the same inbox, and tag each lead by source.

Read the lesson

Goal: Map every lead source, send each one into ServiceAgent, and prove each path with a test lead.

You need: Lessons 3, 5 and 6 built. A list of the client's directories and ad channels. Zapier or Make.com if a source can only email or post leads.

Why this matters

A fleet gets leads from many places. Google. The website. The booking page. Angi or HomeAdvisor. Facebook. Ads. Each source has its own path. One slow path can hide behind fast ones.

Say 9 of 10 sources reply in under a minute. The tenth sends leads to an email address nobody reads. The overall median still looks great. But every lead from that source is lost. The owner pays the directory for leads that never get a reply.

This lesson finds and fixes that path. Then you can show the owner where jobs really come from.

Map every source

Start with a source map. Ask the owner and the office. Check bank statements for directory fees. Check the Google Business Profile.

SourceHow the lead arrivesPath into ServiceAgent
Phone calls (any source)Call to the business numberVoice agent, text-back
Website formForm on the websiteServiceAgent form, or Zapier/Make.com
Booking pageBookingAppointment and contact created
Website chatChatConversations
Directory (Angi, HomeAdvisor)Usually email or the directory's appEmail setup, or Zapier/Make.com
ServiceAgent adsCalls, booking page visits, chatSame as above; tag the source

Check each directory's own lead settings. Many can send leads to an email address. If the email goes to the address connected in Email setup, the lead lands in Conversations. If the directory can connect to Zapier or Make.com, you can create the contact and start the lesson 3 workflow.

Fig 1

How a directory lead gets in

  1. A directory sends a lead
  2. Can it send leads to an email address?YesUse the Email setup address; it lands in ConversationsNoCheck the next way in
  3. Can it connect to Zapier or Make.com?YesCreate the contact; Contact Created starts the lesson 3 workflowNoCheck the directory's own lead settings
  4. Send a test lead and time the reply
Check each directory's own lead settings, then prove the path with a test lead.

Ad leads need a source tag

ServiceAgent runs ads on Google Search, Google Performance Max, Google Maps, Meta Feed and Meta Story. There are no lead-form ads. Leads arrive as phone calls, booking page visits and chats. Nothing tags the ad source by itself. There is no call tracking number per campaign.

So you tag sources by hand. Add a custom field called "Lead source". Make it a Dropdown, not free text. Ask every new customer: "How did you hear about us?" Then pick the answer from the list.

Fig 2

A lead source field the team can count

Add Field: Lead source (Dropdown)

Keylead_source
Help TextAsk: How did you hear about us?
Apply to Entity TypesContact
Show in formsOn, so the team picks a choice
Add Field
One Dropdown choice per source: website, booking page, chat, Google ad, Meta ad, Angi. A fixed list counts each source once.

Build it in ServiceAgent

  1. Build the source map above for the client.
  2. Create the "Lead source" field. Go to Settings → Contacts & Pipeline → Custom fields. Pick type Dropdown. Add one choice per source.
  3. Add the question "How did you hear about us?" to three places. Use the voice agent's questions, the booking page notes and the office's call script.
  4. For each directory, point its lead email at the address in Email setup. Or connect the directory through Zapier or Make.com.
  5. For sources that create a contact, check the lesson 3 workflow fires. Use Contact Created for leads that come in through Zapier or Make.com.
  6. Send one test lead from every source. Use a fresh name for each, such as "Test Angi Lee".
  7. Time the first useful reply for each source. Write it in the source map.
  8. Fix any source that waits. Find where the lead stops. Fix the path. Test it again.
  9. After 30 days, open Contacts → Reports → Lead Sources. Compare it with the "Lead source" field.

Check it works: every source on the map has a test lead with a reply time under the target. Every new contact has a lead source.

Fig 3

Source tagging

  • "Lead source" field as a Dropdown
  • One choice per source
  • Question asked on every new call and booking
  • Lead Sources report checked after 30 days
Ads and directories do not tag themselves, so the team asks.

Report sources to the owner

After 30 days, you can show the owner something new: where their jobs come from. This changes how they spend money.

Make one simple table each month. List each source, the number of new contacts and the number of booked jobs. Use the "Lead source" field and the calendar. Add what the owner pays each source, if they pay one. Then divide the cost by the booked jobs. That is the cost per booked job for each source. ServiceAgent has no screen for this, so you work it out by hand.

Keep it honest. A source with few leads may still book well. A source with many leads may book badly. Show both numbers and let the owner decide. Never move their budget for them. Your job is to make the numbers clear and the same every month. Over a few months, the owner will see which directories earn their fee and which do not. That trust is worth more than any one report.

How business size changes the work

An owner-operator usually has 3 or 4 sources. The map fits on a sticky note, and the main risk is the directory email. A fleet often has 8 or more sources, including paid directories and ads. It needs the full map and a quarterly retest. A multi-location business needs one map per location. The same directory may send leads to different branch emails.

Worked example: Polar Air Services

Polar Air Services has about 20 techs on Growth. You test 6 sources. The figure shows the example results.

Fig 4Example numbers

Polar Air reply times by source

Website form40 seconds
Booking page30 seconds
Website chat20 seconds
Missed call text-back45 seconds
Google ad callAnswered live
Angi2 hours: fail
One slow source hides behind five fast ones.

The median of the 6 tests is under a minute. That looks great. But Angi leads wait 2 hours. You trace the path. Angi sends leads to the owner's old email. They check it twice a day.

You point Angi's lead email at the address in Email setup. The lead now lands in Conversations. The Inbox SLA makes a task at the next hourly check if nobody reads it within 15 minutes. You send a new test. The reply comes in 6 minutes, from a person. That is now within target.

Fig 5

Fixing the Angi path

Before: about 2 hours
  • Angi lead
  • Owner's old email
  • Checked twice a day
After: 6 minutes
  • Angi lead
  • Address in Email setup
  • Lands in Conversations
  • Inbox SLA task if nobody reads it
  • A person replies
Find where the lead waits, change the path, then test again.

The owner pays Angi for these leads. Example input: 30 Angi leads a month. Before the fix, each one waited about 2 hours. Some were surely lost to faster companies.

Common mistakes

  • Reporting only the overall median. One slow source hides behind fast ones. Report each source.
  • Free-text lead sources. "Google", "google ads" and "GGL" become three sources. Use a Dropdown.
  • Assuming ads tag themselves. Nothing tags the ad source by itself. Ask and record it.
  • Testing once. Paths break when a directory changes its settings. Retest every source each quarter.

Do this now

Build a source map for one roster business. List at least 5 sources. For each, write how the lead arrives and the path into ServiceAgent. Mark the one you think is most likely to be slow, and say why.

Practice the conversation

  1. Owner Our leads come from everywhere. Is that a problem?
  2. Operator Not if each one gets a fast reply. I tested all six of your sources.
  3. Owner And?
  4. Operator Five replied in under a minute. Angi took two hours.
  5. Owner Why?
  6. Operator Angi sends leads to your old email. You check it twice a day.
  7. Owner I pay for those leads.
  8. Operator Right. Now they land in your inbox with everything else. If nobody reads one, the team gets a task.
  9. Owner Can you tell me which source books the most jobs?
  10. Operator Yes, once every new customer has a lead source. We ask each one how they heard about you.

Quick check

  1. You send one test lead from each of a fleet's lead sources. Website and ad leads get a reply in under 1 minute. One directory's test lead waits 2 hours. What do you do?
    • Nothing, because most leads come from the fast sources
    • Stop taking leads from that directory
    • Find where that directory's leads land, fix the path, then test again
    • Report only the overall median, since the owner wants one number
  2. A Google ad brings in a phone call. How does the ad source get recorded in ServiceAgent?
    • A call tracking number per campaign tags it
    • The ad's lead form fills the field
    • The team asks "How did you hear about us?" and picks the answer in a `Dropdown` field
    • The `Lead Sources` report detects it from the ad platform
  3. Why make "Lead source" a `Dropdown` instead of a `Text` field?
    • `Dropdown` fields cost fewer credits
    • A fixed list stops one source being spelled many ways
    • Only `Dropdown` fields show in `Conversations`
    • `Text` fields cannot be added to contacts

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community