A shared inbox still needs one owner per conversation.

See how enquiries actually reach a small business here.

I read 642 of the 877 open businesses in Squamish this September, the ones whose site was working and reachable (byImprint intake census, 8 September 2026; 235 sites were unreachable, blocked to a reader, or ruled out by robots rules). Of those, 422, about two in three, route an enquiry through a plain contact form. Another 168, about one in four, give a direct phone number or email with no form in between. The remaining 52 had no working enquiry path I could find. None used a dedicated online system for general enquiries; that kind of software simply is not common here yet.

I also tested whether these paths actually complete: 1,412 attempts across booking, quote, order and enquiry paths town-wide, 1,327 successful, 25 that failed outright, and 60 I could not verify either way (same census, 8 September 2026). That is a 94% completion rate, which means roughly one attempt in twenty either breaks somewhere or cannot be confirmed before anyone reaches the question this guide answers. A message that never arrives does not need an owner. One that lands somewhere unclear does.

This guide assumes the common case in this town: a form or a listed email address feeding one inbox, not a dedicated help desk platform with built-in routing. That covers most businesses here, and it is the arrangement most likely to break quietly.

Define what assignment means.

Assigning a conversation means one person is responsible for the next action. Others can help, but they should not send a separate reply without checking the record first. Make the owner visible in the shared view itself, rather than relying on a private note or a verbal aside that only one other person heard.

If your email tool has assignments and internal notes, agree how to use them consistently. Otherwise a small shared tracker, even a single spreadsheet tab, can link back to the conversation. The rule matters more than the brand of tool behind it.

With 168 of 642 businesses here relying on a bare phone number or email address rather than a routed form, assignment often starts as a manual step: someone has to notice the message arrived at all, in an inbox with no routing logic built in. Say who checks that inbox and how often, in writing, before the volume forces the gap into the open.

Separate reply status from business status.

“Read” does not mean handled. “Replied” does not mean the enquiry is finished. Use a small number of states that tell the team whether it is waiting on them, waiting on the customer, or closed, and keep that list short enough that everyone actually uses it.

If a conversation moves into a quote or booking system, keep a clear reference between the two records. Do not maintain two competing versions of its current status in different tools, because the version nobody checks becomes the one that is wrong.

The 25 paths that failed outright in my read, and the 60 I could not verify, are a reminder that “sent” is not the same as “received”. If your own form tool does not confirm delivery to you, test it the way I tested theirs: send a real message on a normal working day, not immediately after a change, and watch for it to actually land.

Match the channel to the message.

Phone was the most common contact channel among the sites I read, listed 510 times; email followed at 475. Live chat and messaging apps such as WhatsApp were rare, 12 and 9 respectively (byImprint intake census, 8 September 2026; a business can list more than one channel, so these are not 642 separate, mutually exclusive counts).

A phone call and a form submission need different handling in a shared inbox. A call has no written record unless someone makes one; a form submission already carries the customer's own words. Decide, in the same document that defines assignment, who logs a phone enquiry into the shared view, and how soon after the call it needs to appear.

If a chat widget or a messaging link is rare in your sector, as it is here, do not add one just to look responsive. Match the channel to what your actual customers use and what your team can actually keep staffed.

Prevent a collision.

Illustrative example: Alex starts a draft while Jo takes a phone call from the same customer. Jo adds the new detail and alerts the owner. Alex checks that update before sending. If Jo takes over instead, Alex stops drafting and the assignment changes with them, visibly, not as an assumption.

Without that handoff, both people can send a reasonable reply that conflicts with the other, which looks worse to the customer than a slow reply would have. A visible draft indicator can help, but it does not replace the ownership rule underneath it.

If the collision happens over the phone rather than in writing, the same rule applies: whoever answers writes down what changed and who now owns the reply, before hanging up. In a town where phone is the most-listed contact channel, a habit of writing nothing down after a call is where the two-reply problem usually starts.

Agree a useful handover.

Before time off or a shift change, review open conversations with actions due. The incoming owner needs the last meaningful event, what is missing, and the next step. “Keep an eye on this” is too vague to actually transfer responsibility.

Give escalation a destination too. If nobody on the team can answer a question, the record should show who will decide, rather than sitting indefinitely in a general inbox that everyone can see and nobody owns.

Handover matters even more where a business runs its enquiries by hand: 220 of the 642 sites I read handle enquiries through a directed phone or email link, or have no working path at all, rather than a routed form (byImprint intake census, 8 September 2026). That means the message often reaches one specific person directly. If that person is away with no handover note, the enquiry can sit until they are back, not because nobody cares, but because nobody else knew it existed.

Keep saved answers current.

Give each repeated answer an owner, a version and a review date. Keep its approved source beside it, such as the current service page or booking terms, so a check takes one click rather than a memory test.

Retire the previous version the moment a fee, policy or working arrangement changes. A saved answer that quotes last season's price is worse than no saved answer at all, because it looks authoritative while being wrong.

Illustrative example: “Booking changes · version 3 · owner Jo · reviewed 9 September 2026.” Jo checks the wording against the current terms; the person replying checks that it fits this customer before sending. A saved answer, including one drafted with an AI tool, does not approve its own claims; a named owner does.

Test whether the arrangement holds.

Try a duplicate message, a customer reply arriving during drafting, and an absent owner. Check whether the team can handle each case without a private explanation from the founder, because that explanation is exactly what will not exist when it is actually needed.

This is the same discipline I used to test 1,412 paths across the town: send a real message, on a normal day, and watch what actually happens to it, rather than trusting that a process works because it was written down once.

Test the edges too, deliberately. The census did not measure time of day, so this is operational judgement, not a measured figure: decide plainly whether a message that arrives at nine on a Saturday evening waits until Monday, or whether someone actually checks the inbox outside normal hours, and say which choice you have made on the enquiry page itself, so a customer's expectation matches your real staffing rather than a promise nobody was assigned to keep.

Choose new software only when the current tools cannot hold the rule.

Choose new software only when the current tools cannot support the rules above reliably. Adding another inbox can make ownership harder, not easier, if the team has not first agreed where the work actually lives and who is expected to look at it.

A shared inbox with a clear rule can outlast a much bigger team than people expect, including through the busiest weeks of a season here. See CRM or spreadsheet for the point where an inbox, or a spreadsheet, genuinely runs out of road and a dedicated system starts to earn its cost.

• CRM or spreadsheet

Get help if the volume has outgrown a manual fix.

If enquiries are being missed or duplicated often enough to cost real time, a focused discovery session looks at this one workflow and hands you a written recommendation, CA$750, credited toward a related project if you go ahead within 30 days (byImprint pricing, current terms). The session looks at what you actually have running today, not a generic template, before recommending a change.

Most of what is in this guide costs nothing to try first: write the rule down, name the owner, and test it on a normal week before spending on anything new. Only bring in outside help once you can describe precisely where the current arrangement breaks, because that description is most of what a useful recommendation needs to work from.

• Pricing and scope