{"id":3000,"date":"2026-10-29T09:02:37","date_gmt":"2026-10-29T09:02:37","guid":{"rendered":"https:\/\/360dialog.com\/blog\/?p=3000"},"modified":"2026-10-29T12:03:16","modified_gmt":"2026-10-29T12:03:16","slug":"get-chat-vs-building-custom-whatsapp-inbox","status":"publish","type":"post","link":"https:\/\/360dialog.com\/blog\/get-chat-vs-building-custom-whatsapp-inbox\/","title":{"rendered":"get.chat vs Building a Custom WhatsApp Inbox: When to Build and When to Buy"},"content":{"rendered":"\n

A custom WhatsApp inbox pays off when your message data has to stay on servers you control, and get.chat pays off when your team needs to start answering customers without months of development.<\/strong> Every team that answers customers on one WhatsApp number needs a shared place to read, assign, and reply to conversations. Building that place means writing and maintaining the software that receives each message, stores it, shows it to agents, and tracks when a reply is still allowed. Buying it lets your developers spend that time on your own product, while the inbox keeps up with Meta’s changes. 360Dialog includes get.chat, the technology behind 360Dialog Inbox, in its Premium plan at \u20ac99 per number per month.<\/p>\n\n\n\n

<\/p>\n\n\n\n

Key Takeaways<\/h2>\n\n\n\n
    \n
  1. A custom inbox takes 3 to 6 months of engineering before the first agent goes live, and your team needs to maintain it afterwards.<\/li>\n\n\n\n
  2. get.chat is ready in minutes for a team using the hosted inbox and in hours for developers connecting it to your own product.<\/li>\n\n\n\n
  3. Build when compliance requires message data on servers you fully control, or when your team needs more stored history than get.chat keeps.<\/li>\n\n\n\n
  4. The 360Dialog Premium plan at \u20ac99 per number per month includes get.chat as the Inbox, together with the Sendout, Automation, and Measurement add-ons.<\/li>\n<\/ol>\n\n\n\n

    <\/p>\n\n\n\n

    What get.chat Is<\/h2>\n\n\n\n

    get.chat is the technology behind 360Dialog Inbox: a shared WhatsApp inbox for your team and an API to the same conversations for your software. Your developers can add WhatsApp to your product without building the conversation layer. When you turn on the Inbox for a number on the Premium plan, 360Dialog sets it up at that number’s own web address, YOUR_STACK_NAME.inbox.getchat.360dialog.io. Every number runs on its own servers and database.[3]<\/p>\n\n\n\n

    360Dialog, an Official Meta Solution Partner, also runs the Cloud API connection behind the Inbox. It registers the phone number and handles message throughput, the number of messages the number can send per second. Our companion article on get.chat’s architecture<\/a> covers each layer in detail.<\/p>\n\n\n\n

    <\/p>\n\n\n\n

    Build vs Buy at a Glance<\/h2>\n\n\n\n

    Building gives your team full control over code and data, and buying puts an inbox live in minutes with upkeep included. The table compares both paths on the points a build or buy decision turns on.<\/p>\n\n\n\n

    Dimension<\/th>Build (Custom Inbox)<\/th>Buy (get.chat on Premium)<\/th><\/tr><\/thead>
    Upfront cost<\/td>3 to 6 months of engineering salaries and infrastructure<\/td>\u20ac99 per number per month<\/td><\/tr>
    Time to deploy<\/td>3 to 6 months before the first agent goes live<\/td>Minutes for the hosted inbox, hours for an Inbox API integration, days for a self-hosted interface[6]<\/td><\/tr>
    Ongoing maintenance<\/td>Your team handles Cloud API updates, scaling, and bugs<\/td>Included in the subscription<\/td><\/tr>
    Customization<\/td>Unlimited, since your team owns the code<\/td>Hosted inbox with no setup; embedded inbox adjusted through its web address for layout, language, and color; your own branding by hosting the open-source frontend yourself<\/td><\/tr>
    Several systems on one number<\/td>Your team builds a layer that copies each new message to every system<\/td>Built in: every connected service receives every new message<\/td><\/tr>
    Agent interface<\/td>Full control over design<\/td>Hosted by 360Dialog, or the open-source React app hosted and branded by your team<\/td><\/tr>
    Routing and assignment<\/td>Any logic your team can code<\/td>Assignment to users or groups, by your team or by your own service through the API; tags and saved responses[5][10]<\/td><\/tr>
    Data location<\/td>Wherever your team chooses<\/td>360Dialog infrastructure, with separate servers and a separate database for every number<\/td><\/tr>
    Vendor dependency<\/td>Meta’s Cloud API only<\/td>360Dialog and Meta<\/td><\/tr>
    Best fit<\/td>Teams with dedicated platform engineers, a vertical product, or infrastructure they want to extend<\/td>Teams that need an inbox fast or want API access to conversations without building the conversation layer<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    Team size, timeline, and how central WhatsApp conversations are to your product decide which column fits.<\/p>\n\n\n\n

    If the table leaves your team between the two columns, talk to us<\/a> about which parts of the inbox you would still want to build yourself.<\/strong><\/p>\n\n\n\n

    <\/p>\n\n\n\n

    What Building Actually Requires<\/h2>\n\n\n\n

    A custom inbox needs five parts, because the WhatsApp Cloud API only carries the messages. Every step between an incoming message and an agent’s screen is yours to build.<\/p>\n\n\n\n

    Component<\/th>What It Does<\/th>Why It Takes Work<\/th><\/tr><\/thead>
    Webhook consumer<\/td>Receives each new message at the webhook, the web address WhatsApp sends events to, checks each delivery, and queues it<\/td>Must answer each delivery quickly and handle repeated deliveries without duplicating messages<\/td><\/tr>
    Message store<\/td>Keeps messages, status updates, and media references<\/td>Media links from Meta expire; data model, indexing, and retention are yours<\/td><\/tr>
    Agent interface<\/td>Lets agents read and reply to conversations<\/td>Several agents working live at once: a frontend project measured in months<\/td><\/tr>
    Assignment logic<\/td>Sends each conversation to the right agent<\/td>Preventing double replies, spreading the load, and handing over from bot to human<\/td><\/tr>
    Delivery-state tracking<\/td>Tracks sent, delivered, read, and failed statuses<\/td>Must track each conversation’s customer service window, the time in which WhatsApp accepts free-form replies: 24 hours after the customer’s last message or call[2]<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    Each part needs monitoring, error handling, and updates whenever Meta changes the Cloud API. The work grows with every WhatsApp number your team adds.<\/p>\n\n\n\n

    Building the full stack pays off when compliance requires message data on infrastructure you fully control. It also pays off when your team needs more history than get.chat stores: up to 1.5 million messages per number, with the oldest removed first.[1]<\/p>\n\n\n\n

    A product with WhatsApp at its core, such as a CRM, helpdesk, or vertical platform, can keep its own interface and routing logic on top of get.chat. The Inbox API, the REST API of 360Dialog Inbox, provides the data layer underneath.[9] Your service reads and answers conversations and assigns each chat to a user or group.<\/p>\n\n\n\n

    If you decide to build, get API access<\/a> and start from the official WhatsApp Business API connection that the managed layer also runs on.<\/strong><\/p>\n\n\n\n

    <\/p>\n\n\n\n

    What get.chat Handles for Your Team<\/h2>\n\n\n\n

    get.chat runs all five parts as managed services. Your developers maintain none of them:<\/p>\n\n\n\n

      \n
    1. Webhook:<\/strong> each WhatsApp number sends its events to one main webhook. 360Dialog can attach extra webhook URLs to a number, and get.chat delivers each event to every service you connect.[8]<\/li>\n\n\n\n
    2. Message store:<\/strong> get.chat keeps the full history of every chat.<\/li>\n\n\n\n
    3. Agent interface:<\/strong> your team works in the hosted inbox, and an open-source version can be embedded in your own product.[4]<\/li>\n\n\n\n
    4. Assignment:<\/strong> chats go to users or groups, set by your team or by your own service.<\/li>\n\n\n\n
    5. Window tracking:<\/strong> get.chat tracks each conversation’s window. A free-form message sent after the window closes returns HTTP error 453, and your service then sends a template, a message format Meta approves in advance.<\/li>\n<\/ol>\n\n\n\n

      The hosted inbox and the Inbox API share one backend. A reply your service sends through the API shows up in the hosted inbox, and a reply your team types there shows up in the API. A bot can answer first while your team watches the same conversations and takes over when needed. For the setup steps, see our guide to configuring get.chat’s REST API and webhooks<\/a>.<\/p>\n\n\n\n

      The Premium plan costs \u20ac99 per number per month and includes the Inbox, Sendout, Automation, and Measurement add-ons.[7] 360Dialog direct clients on Premium get the Inbox at no extra charge. On the Regular plan at \u20ac49, a number has API access without the Inbox.<\/p>\n\n\n\n

      With the inbox running as a managed service, your team answers customers from the first day and your developers keep their time for your own product.<\/p>\n\n\n\n

      For teams that want API access and a ready-made inbox in one plan, activate your inbox<\/a> on the Premium plan.<\/strong><\/p>\n\n\n\n

      <\/p>\n\n\n\n

      Frequently Asked Questions<\/h2>\n\n\n\n

      Does get.chat Replace the WhatsApp Business API?<\/h3>\n\n\n\n

      No. get.chat is an extension layer on top of the WhatsApp Business API connection provided by 360Dialog. The Cloud API still handles message sending, template management, and phone number registration. get.chat adds the shared inbox, delivery to several webhooks, and the Inbox API on top of that connection.<\/p>\n\n\n\n

      Can I Use get.chat’s API Without the Inbox UI?<\/h3>\n\n\n\n

      Yes. The Inbox API and the inbox UI are independent ways into the same backend. Your service can work entirely through the REST API at \/api\/v1\/, reading chats, sending messages, and assigning, tagging, and resolving conversations. The hosted inbox stays available as a fallback console for your team.<\/p>\n\n\n\n

      What Happens If I Start with get.chat and Later Need to Build Custom?<\/h3>\n\n\n\n

      The Inbox API exposes chats, contacts, and full message history, so the move can happen step by step. Your team builds its own interface on the same API, reads the message history through it, and replaces the managed inbox gradually. get.chat does not lock you into the managed UI.<\/p>\n\n\n\n

      How Does get.chat Handle Multiple WhatsApp Numbers?<\/h3>\n\n\n\n

      Each WhatsApp number gets its own Inbox at its own web address, on its own servers and database. Each Inbox has its own API address, webhook settings, and users. A service that works with several numbers connects to each Inbox separately. The Partner API lets partners create and manage Inboxes programmatically.<\/p>\n\n\n\n

      Is the Embeddable Inbox Customizable Beyond URL Parameters?<\/h3>\n\n\n\n

      Yes. The embedded inbox takes URL parameters such as hide_logo, bg_color, lng for language, and chat_only to hide the sidebar. Full white-labeling, with your own logo, page title, and favicon, runs through the open-source React frontend. Your team hosts its Docker image on your own domain and sets the branding in its settings, without changing code. Teams that prefer not to host anything use the hosted inbox from 360Dialog.<\/p>\n\n\n\n

      <\/p>\n\n\n\n

      Sources<\/h2>\n\n\n\n

      [1] 360Dialog Documentation, “Inbox API.” https:\/\/docs.360dialog.com\/docs\/inbox\/inbox-api Accessed October 29, 2026.<\/p>\n\n\n\n

      [2] Meta for Developers, “Service messages.” https:\/\/developers.facebook.com\/documentation\/business-messaging\/whatsapp\/messages\/send-messages Accessed October 29, 2026.<\/p>\n\n\n\n

      [3] 360Dialog Documentation, “Making Requests” (Inbox API reference). https:\/\/docs.360dialog.com\/docs\/inbox\/inbox-api\/reference\/making-requests Accessed October 29, 2026.<\/p>\n\n\n\n

      [4] get.chat embedding guide. https:\/\/docs.getchat.360dialog.io\/guides\/2-embedding-the-inbox\/. Accessed October 29, 2026.<\/p>\n\n\n\n

      [5] 360Dialog Documentation, “Working Chats” (Hosted Inbox). https:\/\/docs.360dialog.com\/docs\/inbox\/hosted-inbox\/working-chats Accessed October 29, 2026.<\/p>\n\n\n\n

      [6] 360Dialog Documentation, “Inbox Overview.” https:\/\/docs.360dialog.com\/docs\/inbox\/overview Accessed October 29, 2026.<\/p>\n\n\n\n

      [7] 360Dialog pricing. https:\/\/360dialog.com\/pricing. Accessed October 29, 2026.<\/p>\n\n\n\n

      [8] 360Dialog Partner Documentation, “Set multiple webhooks for Phone Number.” https:\/\/docs.360dialog.com\/partner\/onboarding\/webhook-events-and-setup\/set-multiple-webhooks-for-phone-number Accessed October 29, 2026.<\/p>\n\n\n\n

      [9] 360Dialog Documentation, “Managing Conversations” (Inbox API). https:\/\/docs.360dialog.com\/docs\/inbox\/inbox-api\/managing-conversations Accessed October 29, 2026.<\/p>\n\n\n\n

      [10] 360Dialog Documentation, “Assignment” (Inbox API reference). https:\/\/docs.360dialog.com\/docs\/inbox\/inbox-api\/api-ref\/assignment Accessed October 29, 2026.<\/p>\n\n\n\n

      <\/p>\n\n\n\n