Docs
Get started

Inject the assigned agent into any message

The Send Agent command replaces itself with the name of the user currently assigned to the contact. Use it inside outgoing messages, internal notes, or workflow steps so every chat record clearly says who's handling the conversation.

Overview

In a multi-agent inbox it's easy to lose track of who replied to whom. The !AGENT! command pulls the assigned user's first name from your CRM and drops it into the message at send time. Customers see who's behind the keyboard, and your reporting layer sees clean attribution.

★

Combine !AGENT! with internal notifications for clean handoff logs: "Lead assigned to !AGENT!", straight into your team's feed.

Command syntax

!AGENT!

The command takes no arguments. Drop it anywhere inside the message body and Wazzap replaces it with the assigned agent's name.

How it works

  1. The contact has an assigned user in your CRM (for example, the closer who owns the lead in HighLevel).
  2. You compose a message that contains !AGENT!.
  3. Wazzap reads the assignment from the CRM at send time, replaces the command with the agent's name, and dispatches the clean message.
  4. If no user is assigned, Wazzap leaves the command in place or drops it, depending on your sub-account settings. Configure a fallback if you rely on this in customer-facing messages.

Examples

Customer-facing intro

Hi {{contact.first_name}}, you'll be working with !AGENT! today. How can we help?

Output: "Hi Maria, you'll be working with Carlos today. How can we help?"

Internal handoff note

!INTERNAL! Lead just paid. Now assigned to !AGENT!.

Posts a team-only message attributing the closed deal to the right rep. Pairs cleanly with the Internal command.

Reporting tag

Booking confirmed. Closer: !AGENT!. !/DELAY/1000/3000/!

Sends a confirmation that automatically stamps which agent owns the booking, with a 1-3 second delay so it doesn't pile on top of the previous message.

Use cases

  • Multi-agent inboxes. Show the customer who they're chatting with each time the conversation handoffs.
  • Sales attribution. Stamp every closed deal with the rep's name straight into the conversation thread.
  • Internal handoffs. Combine with !INTERNAL! to log assignment changes for the team without writing the customer.
  • Round-robin workflows. When HighLevel rotates leads through reps, use !AGENT! to confirm the assignment in the same message that introduces them.

Important notes

  • The command resolves to the assigned user from your CRM, not the user who triggered the workflow.
  • Behavior with unassigned contacts depends on your sub-account configuration. Test before you ship it to customer-facing messages.
  • The command is case-sensitive. Use !AGENT!.
  • Works alongside any other command. Mix freely with Delay, Spintax, Internal, etc.

Troubleshooting

The customer received the literal !AGENT! string

Two usual causes. Either the message was sent from the phone (WhatsApp app doesn't parse Wazzap commands, send from the CRM's Conversations tab or a workflow step), or the syntax was typed wrong (lowercase, missing exclamation mark, extra spaces). Confirm the exact form !AGENT! and resend.

The wrong agent name appeared

The command pulls the currently assigned user. If a workflow reassigned the lead between steps, later messages will use the new assignment. Check the workflow execution log to confirm the assignment at the moment that step fired.

The command resolved to an empty string

The contact had no assigned user when the message fired. Add an assignment step earlier in the workflow, or set up a fallback default in your sub-account settings.

!

For more context-aware enrichments, see Send source (lead origin) and Send transcription (last voice note text).

Was this page helpful?