Understanding Line Switching

Control which device sends each message — permanently, temporarily, or automatically. WhatSnap gives you three tools: account tags for automatic routing, commands for manual overrides, and a priority hierarchy that ties it all together.

Routing Priority

Before diving into specific tools, understand the hierarchy WhatSnap follows for every outbound message:

Commands always win. If nothing else is set, the default line handles it.

Routing and Your Telephony Provider

Tags and commands work the same whether P2P Messenger is your SMS provider or you run it side-by-side with LeadConnector. The provider setting only decides which messages reach WhatSnap in the first place:

Account Tags

Tags are the primary way to control routing automatically. When a GHL contact has a P2P account tag, every message to that contact routes through the matching device — no manual intervention needed.

Tag Format

Every connected line gets a unique tag that you define:

Assign a Tag to a Contact

Automate Tag Assignment

Use a GHL workflow action Add Contact Tag to assign tags automatically. Common triggers:

• Lead assigned to a specific salesperson
• Contact reaches a pipeline stage
• Inbound message received on a specific line
• Contact tagged with a geographic or language-based label

Tag Best Practices

• One account tag per contact. If a contact has two, WhatSnap uses the most recently added one.
• Clean up disconnected lines. If you permanently remove a device, delete its tag from GHL to prevent routing to a dead line.
• Use descriptive names. p2p-account-sales-mark is better than p2p-account-line2. You can edit names in WhatSnap Manager → Lines → three dots → Edit Tag.

Commands

Commands give you per-message control over line routing. When you include a command at the start of your message, WhatSnap:

1. Reads the command to determine which line to use
2. Strips the command before sending — the recipient never sees it
3. Shows the full message (with command) in your GHL conversation for reference

Where to Use Commands

#switch — Permanent Reassignment

Changes the line assigned to this contact going forward. All future messages — and every subsequent SMS action in the workflow — route through the new device.

Example in a workflow SMS action:

#switch|p2p-account-sales-mark
Hey {{contact.first_name}}! This is Mark from Rockstar Agency.

In this workflow, the Customer Booked Appointment trigger fires and the SMS action sends the message from Mark's line (p2p-account-sales-mark). Because it uses #switch, this contact is now permanently assigned to Mark's device — every future message will go through that line.

What the contact receives:

Hey John! This is Mark from Rockstar Agency.

The #switch command is invisible to them — but you'll see it in your GHL conversation.

#switch_unique — One-Time Override

Sends this specific message from a different line without changing the contact's permanent assignment. After this message, routing returns to whatever tag or default was active before.

Example:

#switch_unique|p2p-account-ceo
Hi {{contact.first_name}}, just wanted to personally thank you.

In this workflow, a Condition checks which user is assigned to the contact. If the assigned user is "Nicole M." (the CEO), the SMS action uses #switch_unique to send one message from Nicole's line (p2p-account-ceo). The contact's permanent line assignment stays unchanged — only this specific message goes through Nicole's device.

Command Format

The command must follow this exact structure:

#switch|p2p-account-tagname
Your message here

Common Mistakes

These examples will NOT work:

• Hello! #switch|sales — Command not at start (must be first)
• #switch | sales Hello — Spaces around the pipe (no spaces allowed)
• #switch|sales(Hello) — No space before message content

Practical Use Cases

Sales → Support handoff:

#switch|p2p-account-support
Hello Sarah, our tech team will take it from here.

Manager check-in (without taking over the conversation):

#switch_unique|p2p-account-ceo
Hey, just checking in — how's everything going?

Automated routing via workflow:

Create a workflow with trigger Tag Added → route-to-closers, then use a Send SMS action with:

#switch|p2p-account-closers
Great news! Our pricing specialist will follow up shortly.

Choosing the Right Method

Using Custom Values

GHL custom values work inside any message body — including messages with switch commands. WhatSnap receives the final, personalized text after GHL replaces the variables.

Common Workflow Patterns

Lead Follow-Up Sequence

Appointment Confirmation + Reminder

Volume Considerations

Every message triggers a send from your physical device. For sustainable volume:

• Warm up new lines — Start with 10-20 messages/day, increase gradually. See Line Warm-Up.
• Safe daily range — 200-300 messages per line
• Use multiple lines — Split high-volume campaigns across lines using tags or switch commands