{"id":261,"date":"2026-10-25T13:04:02","date_gmt":"2026-10-25T13:04:02","guid":{"rendered":"https:\/\/vectalk.com.br\/blog\/whatsapp-multi-agent-api\/"},"modified":"2026-10-25T13:12:03","modified_gmt":"2026-10-25T13:12:03","slug":"whatsapp-multi-agent-api","status":"publish","type":"post","link":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-multi-agent-api\/","title":{"rendered":"Multiple agents on the same WhatsApp number: how it works with the API"},"content":{"rendered":"\n<p><em>Updated on October 25, 2026<\/em><\/p>\n\n\n\n<p>There are two ways to have several agents on the same WhatsApp number: the linked devices of the WhatsApp Business app, which have a device limit, or the official WhatsApp Business API, where the number is run by a system and agents work in a shared inbox, with no cap on people set by Meta. With the API, routing, history and permissions live in your software. With coexistence, the phone can even keep working alongside it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The limits of the WhatsApp Business app<\/h2>\n\n\n\n<p>The app was built for manual use. According to the WhatsApp Help Center, a business account can link up to four devices; the multi-agent feature raises that to up to 10, depending on the benefits of subscriptions such as Meta Verified. That works for a small shop, but it breaks down as the team grows:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Everyone sees everything.<\/strong> There is no queue and no &#8220;mine&#8221; or &#8220;yours&#8221;. Two agents answer the same customer, or nobody does.<\/li>\n\n\n<li><strong>No per-person metrics.<\/strong> You cannot tell who replied, how fast, or how many chats each person resolved.<\/li>\n\n\n<li><strong>Dependence on the primary phone.<\/strong> If the primary device goes unused for about 14 days, linked devices are disconnected.<\/li>\n\n\n<li><strong>No integrations.<\/strong> The app does not talk to your CRM, ERP or bot.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">How the API solves it: the number becomes a system<\/h2>\n\n\n\n<p>On the official API, the number is not on a phone. Every incoming message reaches your server through a webhook, and every reply goes out through an HTTP call. An &#8220;agent&#8221; is not a device linked to WhatsApp but a user of your system. That is why Meta does not limit how many people can answer: the limit is your software&#8217;s.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Aspect<\/th><th>App with linked devices<\/th><th>API with a shared inbox<\/th><\/tr><\/thead><tbody><tr><td>Number of agents<\/td><td>Up to 4 devices (up to 10 with multi-agent)<\/td><td>Set by your system<\/td><\/tr><tr><td>Routing<\/td><td>Manual<\/td><td>Automatic, rule-based<\/td><\/tr><tr><td>History<\/td><td>On the device<\/td><td>In your database<\/td><\/tr><tr><td>Per-agent metrics<\/td><td>No<\/td><td>Yes, from the events<\/td><\/tr><tr><td>Bot and AI<\/td><td>Not native<\/td><td>Part of the same flow<\/td><\/tr><tr><td>Permissions<\/td><td>Whoever has the device sees everything<\/td><td>Per team, queue or role<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Shared inbox architecture<\/h2>\n\n\n\n<p>A multi-agent setup on the API has five parts:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Webhook receiver.<\/strong> Receives Meta&#8217;s events, returns <code>200<\/code> quickly and pushes the event onto a queue. Do no heavy work here.<\/li>\n\n\n<li><strong>Processor.<\/strong> Reads the queue, stores messages and statuses, opens or reopens the conversation, and calls the routing engine.<\/li>\n\n\n<li><strong>Routing engine.<\/strong> Decides who handles it: the bot, a department queue or a specific agent.<\/li>\n\n\n<li><strong>Agent interface.<\/strong> Assigned conversations, history and a reply box, updated in real time (WebSocket or similar).<\/li>\n\n\n<li><strong>Sending layer.<\/strong> A single layer that calls the API, stores the returned <code>wamid<\/code> and handles errors.<\/li>\n\n<\/ol>\n\n\n\n<p>Two webhook details shape the design. Meta&#8217;s <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/webhooks\/overview\" target=\"_blank\" rel=\"noreferrer noopener\">webhooks overview<\/a> says unacknowledged events are retried for up to 7 days and that this can produce duplicate notifications. So:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Deduplicate on the message <code>id<\/code> (<code>wamid<\/code>).<\/strong> A unique constraint in the database is enough.<\/li>\n\n\n<li><strong>Do not rely on arrival order.<\/strong> Sort messages by the event <code>timestamp<\/code>, not by when the webhook arrived.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Conversation states<\/h2>\n\n\n\n<p>A support conversation needs clear states. A simple model:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>State<\/th><th>Meaning<\/th><th>Who acts<\/th><\/tr><\/thead><tbody><tr><td><code>bot<\/code><\/td><td>Bot or automatic message handling it<\/td><td>System<\/td><\/tr><tr><td><code>queued<\/code><\/td><td>Waiting for an agent in a department<\/td><td>Routing engine<\/td><\/tr><tr><td><code>assigned<\/code><\/td><td>One agent owns the conversation<\/td><td>Agent<\/td><\/tr><tr><td><code>waiting_customer<\/code><\/td><td>Agent replied, waiting for the customer<\/td><td>System watches the 24-hour window<\/td><\/tr><tr><td><code>closed<\/code><\/td><td>Resolved<\/td><td>Reopens if the customer writes again<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>The <code>waiting_customer<\/code> state matters because of the 24-hour customer service window: if the customer takes too long and the window closes, the agent can only resume with a template.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Routing rules<\/h2>\n\n\n\n<p>No rule fits every case. The most common ones:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Rule<\/th><th>How it works<\/th><th>When to use it<\/th><\/tr><\/thead><tbody><tr><td>Round robin<\/td><td>Next available agent on the list<\/td><td>Similar agents, similar demand<\/td><\/tr><tr><td>Least busy<\/td><td>Agent with the fewest open chats<\/td><td>Chats of varying length<\/td><\/tr><tr><td>By department<\/td><td>Bot asks the topic and routes to the right queue<\/td><td>Separate sales, support and billing<\/td><\/tr><tr><td>Sticky<\/td><td>Customer goes back to their last agent, if available<\/td><td>Consultative sales, account portfolios<\/td><\/tr><tr><td>Manual (pull from queue)<\/td><td>Agent picks the next chat<\/td><td>Small teams, complex cases<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>In practice, combine them: the bot or <a href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-welcome-away-message\/\">welcome message<\/a> asks the topic, the chat goes to that department&#8217;s queue, and within the queue you use least busy, with stickiness for returning customers.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example: conflict-free assignment in PostgreSQL<\/h3>\n\n\n\n<p>The most common bug is two agents grabbing the same chat. With <code>FOR UPDATE SKIP LOCKED<\/code>, each transaction locks the conversation it is assigning and skips those another transaction already holds:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code class=\"language-sql\">-- Assign the oldest queued conversation to the agent with the fewest open chats\nWITH next_conv AS (\n  SELECT id\n  FROM conversations\n  WHERE state = 'queued' AND department = 'support'\n  ORDER BY queued_at\n  LIMIT 1\n  FOR UPDATE SKIP LOCKED\n),\nagent AS (\n  SELECT a.id\n  FROM agents a\n  LEFT JOIN conversations c ON c.agent_id = a.id AND c.state = 'assigned'\n  WHERE a.online AND a.department = 'support'\n  GROUP BY a.id, a.max_concurrent\n  HAVING COUNT(c.id) &lt; a.max_concurrent\n  ORDER BY COUNT(c.id)\n  LIMIT 1\n)\nUPDATE conversations\nSET state = 'assigned', agent_id = (SELECT id FROM agent), assigned_at = now()\nWHERE id = (SELECT id FROM next_conv)\n  AND EXISTS (SELECT 1 FROM agent)\nRETURNING id, agent_id;<\/code><\/pre>\n\n\n\n<p>Run it when a chat enters the queue and when an agent frees up. The <code>max_concurrent<\/code> field keeps anyone from getting more chats than they can handle.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Operating best practices<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Show who is replying.<\/strong> Prefix messages with the agent&#8217;s name (&#8220;<em>Ana:<\/em>&#8220;). The customer knows who they are talking to and handoffs stay transparent.<\/li>\n\n\n<li><strong>Hand off with context.<\/strong> When transferring a chat, add an internal note. The customer should not have to repeat everything.<\/li>\n\n\n<li><strong>Mark as read only when someone has read it.<\/strong> The <code>read<\/code> status shows the two blue ticks to the customer; send it when the agent opens the chat, not when the webhook arrives.<\/li>\n\n\n<li><strong>One sending path.<\/strong> Bot, agents and automations should all go through the same layer, so you respect the number&#8217;s throughput and log everything.<\/li>\n\n\n<li><strong>Least privilege.<\/strong> Agents see their own queue; supervisors see the team. The guide on <a href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-business-account-security\/\">business account security<\/a> covers portfolio access and tokens.<\/li>\n\n\n<li><strong>Measure.<\/strong> First response time, handling time and satisfaction per agent and per queue. See <a href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-customer-service-metrics\/\">WhatsApp support metrics<\/a>.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Coexistence: the phone keeps working<\/h2>\n\n\n\n<p>With coexistence, the same number runs on the WhatsApp Business app and the API at the same time. The owner can keep replying from the phone while the team uses the inbox. According to Meta&#8217;s <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/embedded-signup\/onboarding-business-app-users\" target=\"_blank\" rel=\"noreferrer noopener\">coexistence documentation<\/a>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Messages sent from the app reach your system through the <code>smb_message_echoes<\/code> webhook. Show them in the conversation history, or agents will not know the customer has already been answered.<\/li>\n\n\n<li>The app supports up to four companion devices. Messages sent from unsupported companions (such as WhatsApp for Windows) do not trigger webhooks and will not show up in your system.<\/li>\n\n\n<li>Throughput for coexistence numbers is fixed at 20 messages per second.<\/li>\n\n\n<li>App tools such as quick replies, labels, greeting and away messages are not supported on the Cloud API.<\/li>\n\n\n<li>If the primary device is inactive for about 14 days, Meta sends an <code>account_update<\/code> with <code>PARTNER_REMOVED<\/code> and the API connection drops.<\/li>\n\n<\/ul>\n\n\n\n<p>For multi-agent support, the rule of thumb is: the phone becomes one more &#8220;agent&#8221;, and your system has to treat its messages that way. The article on <a href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-coexistence-what-syncs\/\">what syncs in coexistence<\/a> goes through each item.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to do this with Vectalk<\/h2>\n\n\n\n<p>Vectalk is the API layer: it delivers Meta&#8217;s webhooks to your system and sends replies through the official Cloud API. You can register several URLs per instance with <code>POST \/api\/webhooks<\/code> (for example, your inbox and your CRM receiving the same event), send with <code>POST \/api\/messages<\/code>, and mark as read with the same endpoint using <code>status: \"read\"<\/code>. Vectalk supports coexistence, so the number can stay on the app. The inbox and routing rules belong to your software. Documentation at <a href=\"https:\/\/docs.vectalk.com.br\/concepts\/webhooks\">docs.vectalk.com.br<\/a> and sign-up at <a href=\"https:\/\/apps.vectalk.com.br\/register\">apps.vectalk.com.br\/register<\/a>.<\/p>\n\n\n\n<p>If you plan to put a bot in front of your agents, see also <a href=\"https:\/\/vectalk.com.br\/blog\/en\/ai-appointment-scheduling-whatsapp\/\">AI scheduling on WhatsApp<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently asked questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">How many agents can I have on one number with the API?<\/h3>\n\n\n\n<p>Meta does not limit the number of agents on the API, because they are not WhatsApp devices but users of your system. The practical limit is your software and the number&#8217;s sending capacity.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I use WhatsApp Web together with the API?<\/h3>\n\n\n\n<p>Only with coexistence, where WhatsApp Web acts as a companion device of the app. Messages sent from it reach your system through the <code>smb_message_echoes<\/code> webhook. Without coexistence, a number registered on the API is not available in the app or on WhatsApp Web.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do I stop two agents from answering the same customer?<\/h3>\n\n\n\n<p>Assign the conversation to an owner before showing the reply box, with a database lock (like <code>FOR UPDATE SKIP LOCKED<\/code> in the example). Everyone else sees the chat as read-only.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does the customer see the agent&#8217;s name?<\/h3>\n\n\n\n<p>The customer sees the business display name. If you want to show who is handling the chat, include the name in the message text.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do I need one number per department?<\/h3>\n\n\n\n<p>No. One number with department queues is usually simpler for the customer. Separate numbers make sense for different brands or operations.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p><strong>Official sources consulted on October 25, 2026:<\/strong> <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/webhooks\/overview\" target=\"_blank\" rel=\"noreferrer noopener\">Webhooks overview<\/a>, <a href=\"https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/embedded-signup\/onboarding-business-app-users\" target=\"_blank\" rel=\"noreferrer noopener\">Coexistence: onboarding WhatsApp Business app users<\/a>, <a href=\"https:\/\/faq.whatsapp.com\/395911122612120\/\" target=\"_blank\" rel=\"noreferrer noopener\">WhatsApp Help Center: multi-agent<\/a>, <a href=\"https:\/\/docs.vectalk.com.br\/concepts\/webhooks\">Vectalk docs: webhooks<\/a>, <a href=\"https:\/\/docs.vectalk.com.br\/api-reference\/messages\/mark-as-read\">Vectalk docs: mark as read<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>How to run several agents on one WhatsApp number: app limits, shared inbox architecture with the official API, routing rules and the role of coexistence.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[1],"tags":[],"class_list":["post-261","post","type-post","status-publish","format-standard","hentry","category-blog"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>WhatsApp multi-agent support with the API | Vectalk<\/title>\n<meta name=\"description\" content=\"WhatsApp multi agent support on the Business API: many agents on one number, shared inbox architecture, routing rules and coexistence.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-multi-agent-api\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"WhatsApp multi-agent support with the API | Vectalk\" \/>\n<meta property=\"og:description\" content=\"WhatsApp multi agent support on the Business API: many agents on one number, shared inbox architecture, routing rules and coexistence.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-multi-agent-api\/\" \/>\n<meta property=\"og:site_name\" content=\"Blog Vectalk\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-25T13:04:02+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-25T13:12:03+00:00\" \/>\n<meta name=\"author\" content=\"wanderleyfcunha\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"wanderleyfcunha\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-multi-agent-api\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-multi-agent-api\\\/\"},\"author\":{\"name\":\"wanderleyfcunha\",\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/#\\\/schema\\\/person\\\/ff36ecd9d8257856f227f8e5d639db2b\"},\"headline\":\"Multiple agents on the same WhatsApp number: how it works with the API\",\"datePublished\":\"2026-10-25T13:04:02+00:00\",\"dateModified\":\"2026-10-25T13:12:03+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-multi-agent-api\\\/\"},\"wordCount\":1426,\"articleSection\":[\"Blog\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-multi-agent-api\\\/\",\"url\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-multi-agent-api\\\/\",\"name\":\"WhatsApp multi-agent support with the API | Vectalk\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/#website\"},\"datePublished\":\"2026-10-25T13:04:02+00:00\",\"dateModified\":\"2026-10-25T13:12:03+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/#\\\/schema\\\/person\\\/ff36ecd9d8257856f227f8e5d639db2b\"},\"description\":\"WhatsApp multi agent support on the Business API: many agents on one number, shared inbox architecture, routing rules and coexistence.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-multi-agent-api\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-multi-agent-api\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/en\\\/whatsapp-multi-agent-api\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Multiple agents on the same WhatsApp number: how it works with the API\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/\",\"name\":\"Blog Vectalk\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/vectalk.com.br\\\/blog\\\/#\\\/schema\\\/person\\\/ff36ecd9d8257856f227f8e5d639db2b\",\"name\":\"wanderleyfcunha\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/21c37077f1731eb558973f27a7b647d55f72fde5200a843ac5f5345b247ea725?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/21c37077f1731eb558973f27a7b647d55f72fde5200a843ac5f5345b247ea725?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/21c37077f1731eb558973f27a7b647d55f72fde5200a843ac5f5345b247ea725?s=96&d=mm&r=g\",\"caption\":\"wanderleyfcunha\"},\"sameAs\":[\"https:\\\/\\\/vectalk.com.br\\\/blog\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"WhatsApp multi-agent support with the API | Vectalk","description":"WhatsApp multi agent support on the Business API: many agents on one number, shared inbox architecture, routing rules and coexistence.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-multi-agent-api\/","og_locale":"en_US","og_type":"article","og_title":"WhatsApp multi-agent support with the API | Vectalk","og_description":"WhatsApp multi agent support on the Business API: many agents on one number, shared inbox architecture, routing rules and coexistence.","og_url":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-multi-agent-api\/","og_site_name":"Blog Vectalk","article_published_time":"2026-10-25T13:04:02+00:00","article_modified_time":"2026-10-25T13:12:03+00:00","author":"wanderleyfcunha","twitter_card":"summary_large_image","twitter_misc":{"Written by":"wanderleyfcunha","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-multi-agent-api\/#article","isPartOf":{"@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-multi-agent-api\/"},"author":{"name":"wanderleyfcunha","@id":"https:\/\/vectalk.com.br\/blog\/#\/schema\/person\/ff36ecd9d8257856f227f8e5d639db2b"},"headline":"Multiple agents on the same WhatsApp number: how it works with the API","datePublished":"2026-10-25T13:04:02+00:00","dateModified":"2026-10-25T13:12:03+00:00","mainEntityOfPage":{"@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-multi-agent-api\/"},"wordCount":1426,"articleSection":["Blog"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-multi-agent-api\/","url":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-multi-agent-api\/","name":"WhatsApp multi-agent support with the API | Vectalk","isPartOf":{"@id":"https:\/\/vectalk.com.br\/blog\/#website"},"datePublished":"2026-10-25T13:04:02+00:00","dateModified":"2026-10-25T13:12:03+00:00","author":{"@id":"https:\/\/vectalk.com.br\/blog\/#\/schema\/person\/ff36ecd9d8257856f227f8e5d639db2b"},"description":"WhatsApp multi agent support on the Business API: many agents on one number, shared inbox architecture, routing rules and coexistence.","breadcrumb":{"@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-multi-agent-api\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/vectalk.com.br\/blog\/en\/whatsapp-multi-agent-api\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-multi-agent-api\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/vectalk.com.br\/blog\/"},{"@type":"ListItem","position":2,"name":"Multiple agents on the same WhatsApp number: how it works with the API"}]},{"@type":"WebSite","@id":"https:\/\/vectalk.com.br\/blog\/#website","url":"https:\/\/vectalk.com.br\/blog\/","name":"Blog Vectalk","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/vectalk.com.br\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/vectalk.com.br\/blog\/#\/schema\/person\/ff36ecd9d8257856f227f8e5d639db2b","name":"wanderleyfcunha","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/21c37077f1731eb558973f27a7b647d55f72fde5200a843ac5f5345b247ea725?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/21c37077f1731eb558973f27a7b647d55f72fde5200a843ac5f5345b247ea725?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/21c37077f1731eb558973f27a7b647d55f72fde5200a843ac5f5345b247ea725?s=96&d=mm&r=g","caption":"wanderleyfcunha"},"sameAs":["https:\/\/vectalk.com.br\/blog"]}]}},"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/posts\/261","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/comments?post=261"}],"version-history":[{"count":2,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/posts\/261\/revisions"}],"predecessor-version":[{"id":442,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/posts\/261\/revisions\/442"}],"wp:attachment":[{"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/media?parent=261"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/categories?post=261"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vectalk.com.br\/blog\/wp-json\/wp\/v2\/tags?post=261"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}