AI agent on your Google listing, Meta's agent in your DMs, nobody in your inbox: the orphan-channel map, 2026 edition

In 2026 every big platform answers the first message in its own app, and none of them answers yours. Meta's Business Agent answers WhatsApp and Instagram DMs¹. Google is piloting an AI agent in Business Profile messages for some US businesses³. Thumbtack's Front Desk auto-replies inside Thumbtack⁴. Your info@ inbox, your website form and the lead emails from directories have no agent at all. Those are the orphan channels. In Leadferno's 2024 test of 225 small-business contact forms, 42.6% of inquiries got no reply⁷.

This runbook maps your channels, tests each one, and closes the orphans. It does not ask you to buy anything.

What this runbook does, how long it takes, and what access you need#

This runbook produces one table: every channel a customer can use to reach you, who answers it first, what is left after that first answer, and who owns the rest. Budget 90 minutes for the first pass. Budget 15 minutes a month after that.

Prerequisites. Do not start until you have all five.

• Owner access to your Google Business Profile. A manager role may not show Messages settings.
• Admin access to Meta Business Suite for WhatsApp Business and Instagram, if you use them.
• Login to every marketplace or directory you pay for or are listed on: The Knot, WeddingWire, Thumbtack, Yelp, Bark, Angi.
• Admin access to your email domain (Google Workspace, Microsoft 365 or your host), so you can see forwarding rules and spam folders.
• A personal email address and phone that is not on any business account. You will use it to send test inquiries as a customer would.

Role-based access matters here. If a former assistant or agency still holds the only admin role on a listing, fix that first. You cannot test a channel you cannot open.

Use this runbook if, and do not use it if#

The orphan-channel runbook fits a small business that takes written inquiries in three or more places. Check the filter before you start.

Who answers which channel in 2026? The orphan-channel map#

The orphan-channel map below lists each common channel, the platform agent that answers it first, and what that agent leaves for a person. Each row comes from the platform's own announcement or documentation, or from trade-press reporting where no documentation exists. Copy it, delete the rows you do not use, and fill in the last two columns during the pre-flight test.

Channel	Who answers first in 2026	What's left for a person	Your test result (time to first reply)	Owner and follow-up rule
WhatsApp Business	Meta Business Agent; TechCrunch reports it is charged through WhatsApp Business Premium tiers1	Any chat it hands off: the agent "stops answering that chat"2
Instagram DMs	Meta Business Agent1	Handoffs, custom quotes, follow-up
Google Business Profile messages	Google's AI agent, US pilot, not on every profile3	Everything under "Needs your attention"3
Thumbtack messages	Front Desk auto-reply, "within an average of two minutes"4	Everything after the auto-reply
Yelp quote requests	AI guidance helps the owner write replies; Yelp Host and Receptionist cover calls5	The written reply and every follow-up
Phone, including Google's automated calls	Whoever picks up; Google's AI places calls to "confirm price and availability"6	A price, a time, a call back
Email to info@, hello@, bookings@	No platform agent	Everything
Website contact form	No platform agent; arrives as email	Everything
Marketplace and directory lead emails	No platform agent outside each app	Everything

Checked 1 October 2026. Google's Business Profile agent is an unstable US pilot with no official Google documentation, per Partoo. Confirm each row against current platform pages before you rely on it.

Read the bold rows twice. They are the channels where a quote, a contract question or a wedding date tends to arrive. They are also the rows where the second column is empty. For a channel-by-channel look at the two platform agents, see what Meta's Business Agent answers and what Google's "Handled by your AI agent" means.

Pre-flight: send one test inquiry to every channel#

The pre-flight test is a dry run: you write to your own business as a customer would, on every channel, and record what happens. Do this before you change any setting. The results are your baseline.

1. Write one realistic question. Use a question that needs a price and a date, for example "What would it cost for 14 March, and is that date open?" A question about opening hours will pass every test and tell you nothing.
2. Send it from your personal accounts to every row in the map. Use the same wording each time. Note the time sent.
3. Do not touch the business side for 24 hours. You are testing what happens without you.
4. Record the first reply on each channel. Write down the time, who or what sent it, and whether it answered the question or only acknowledged it.
5. Record what happened next. Did anyone follow up after 48 hours? Did any reply offer a time?

Verification check: every row in your copy of the map now has an entry in the "test result" column. If a row is blank because the message never arrived anywhere, mark it BROKEN. Leadferno found 4.8% of the forms it tested were broken⁷. A broken form outranks every other fix on this list.

How to close the orphan channels, step by step#

Closing an orphan channel means three things: one place it lands, one person who owns it, and one rule for what happens if the customer goes quiet. Run these steps in order. Each step has a check and an exit if it fails.

1. Fix anything marked BROKEN. Send the test again after the fix. Verify: the message arrives in the main inbox, not spam or a filtered tab. If it still fails: stop and fix delivery before you go on. Our ten-minute contact-form test covers the delivery checks.
2. Route every channel that arrives as email to one address. That covers the website form, info@, bookings@ and marketplace notification emails. Use forwarding rules, not a second login. Verify: send one test to each source and confirm all of them land at that one address. If one does not: check whether the platform lets you change its notification address. Some send only to the account email.
3. Name one owner per row. Write a name, not "the team". Verify: every row in the "Owner" column has one name. If two names: pick one. Shared ownership is how the inbox in your test went 24 hours without a reply.
4. Set a check schedule for app-only channels. DMs, Google messages and in-app marketplace chats cannot be forwarded to email in most cases. Set two fixed times a day to open them. Verify: the times are in the owner's calendar. If a platform agent hands off a chat, treat the handoff notice as a new inquiry with a reply-by time.
5. Write one follow-up rule per row. For example: "If no reply in two days, send one message with a held time. If no reply two days later, send one closing message. Then stop." Verify: the rule fits in one sentence. Pied Piper's 2026 mystery shop of 3,211 home-services inquiries found 72% got no follow-up at all⁸. A one-sentence rule beats a sequence nobody runs.
6. Log the same customer once. When one person writes on two channels, keep one record and reply in the channel they used last. Verify: in next week's inquiries, no customer got two different answers.
7. Repeat the pre-flight test. Same question, same channels, seven days later. Verify: every orphan row now shows a reply inside your target time and a follow-up at 48 hours.

Step 2 is the step that does the most work. Customers do not pick the channel you prefer. BrightLocal's 2026 survey of 1,002 US adults found that after reading reviews, 54% go to the business's website and 20% contact the business directly⁹. The website route ends at the form, which is an email, which is an orphan.

Three ways this fails, and the exact fix#

The orphan-channel runbook fails in production for three common reasons. None of them is a software fault. Each one has a fix you can apply the same day.

Failure 1: the forwarding rule works, then silently stops#

A forwarding rule that worked in week one can stop in week six. Typical causes: someone changes a password, a platform changes its sender address, or a spam filter starts catching the forwarded copy. Nobody notices, because a missing email makes no noise.

Fix: put a monthly test inquiry in the calendar for each forwarded source. If a test fails, the rollback trigger is simple: switch that source back to landing in the original inbox, tell the owner to check it daily, and repair the rule before switching again.

Failure 2: the platform agent hands off and nobody picks it up#

A handoff from a platform agent looks like progress, and it often is not. Meta's agent goes quiet in a chat after it hands off, and the handoff notice is a fixed message². Google's pilot puts passed conversations under "Needs your attention", with a "Customer handoff" setting that notifies the owner³. Both leave the reply, the time and the follow-up with a person.

Fix: turn on every handoff notification the platform offers, and route it to the same owner as the email row. Treat each handoff as a new inquiry with the same reply-by target. Then check the handoff pile at the two scheduled times, even if no notification came.

Failure 3: the same questions eat the owner's day#

Consolidating channels can make the volume visible all at once. A thread in r/smallbusiness (90+ comments, September 2026) came from an owner whose business took off on social media and who was "answering the same questions over and over (our pinned post has all of the answers)". A pinned post did not stop the questions. Customers asked anyway, in whatever channel they were already using.

Fix: write the ten questions you answer most, with the exact answer, on one page. Use it for every channel. Our facts-sheet guide shows what goes on it and what must never be improvised, such as discounts.

Rollback and the monthly health check#

The rollback for this runbook is short, because nothing in it deletes data. If consolidation causes confusion, undo the forwarding rules from Step 2 one source at a time, and keep the owner names and follow-up rules. Owners and rules work even without forwarding.

Run the health check on the first working day of each month:

1. Re-send the pre-flight question to every row. Compare the reply times to last month.
2. Re-check the platform rows. Google's pilot has appeared and disappeared on profiles³, and Meta's terms may change. Update the "who answers first" column.
3. Count last month's inquiries per channel and how many got a follow-up. If you want a fuller version of this count, the Lost Lead Audit walks through 90 days of inquiries.

Health is one sentence: every row has an owner, every test got a reply inside the target, and every quiet customer got a follow-up.

Where Valet fits#

Valet covers the bold rows. You forward info@, hello@ or bookings@ to a private Valet address, and Valet answers email, website forms and marketplace lead emails from your own price list, calendar and policies. Each inquiry gets one record with a state, a next step and a time, in the Valet Inquiry States from New to Booked. Valet follows up twice at most, each time with something useful, then stops and tells you why. Money, complaints and contracts come to you with one-tap replies. Keep Meta's and Google's agents for their own apps. To see what your orphan rows held last quarter, start with the free lead check: forward 10 to 20 recent inquiries and see what went unanswered.