Feature Request

Platform Problem Our platform currently restricts users to exporting data within a 1-year range from today’s date, aiming to avoid exceeding the file size limit. However, an oversight in the date picker functionality prevents users from selecting a date range that extends beyond the current calendar year. Desired Outcome The goal is to modify the date picker to enable users to choose any date from the past as the starting point for their data export, provided the total duration does not surpass 365 days. This adjustment will ensure flexibility while adhering to the file size limitations.

I would like to be able to delete or edit a message that I sent by mistake on the Messages module, and for it to also be removed for edited rom the recipient's device. 🔴 Important Note: This is NOT a limitation on respond.io . This is a limitation set by Meta's team to all WhatsApp API accounts.

Business Problem: Customers who edit WhatsApp message templates directly on Meta's page (rather than in Respond.io ) must manually sync each affected channel in Respond.io before the changes take effect. For customers managing multiple WhatsApp channels, this becomes a repetitive, time-consuming, and error-prone manual process. There is currently no way to sync templates across multiple channels at once, forcing users to repeat the same manual step per channel every time a template is updated on Meta. Desired Outcome: Automatically detect and sync template changes made on Meta without requiring a manual "Sync Templates" action. Support bulk/auto-sync across all WhatsApp channels in a workspace, rather than one channel at a time. Notify the user when a sync has occurred (or if a sync fails), so they know templates are up to date without checking manually.

Business Problem: When agents handle calls with customers who speak a different language, the auto-generated call transcript is only available in the language spoken during the call. Teams that operate across multiple regions — or where supervisors, and managers speak a different language than the customer — have no way to read or review those transcripts in a language they understand. This gap is further compounded by two additional challenges. First, regional language variations: a team in Spain reviewing calls in Latin American Spanish, or a team in Brazil reviewing calls in European Portuguese, may encounter translated content that doesn't reflect the correct regional terminology, tone, or vocabulary. Second, look-alike languages: languages that are closely related or share significant similarities — such as Spanish and Portuguese, Malay and Indonesian, Hindi and Urdu, or Serbian and Croatian — are frequently misidentified by automatic language detection. When the system selects the wrong base language, the transcript or translation can be inaccurate or misleading, eroding trust in the tool and creating extra manual work to verify what was actually said. Desired Outcome: Users should be able to manually select both the source language (what was spoken during the call) and the target language for translation directly within the interface. Giving users explicit control over language selection is especially critical for look-alike language pairs, where automatic detection is prone to error. This ensures transcripts are accurate, culturally appropriate, and trustworthy across all the languages and regions a business operates in.

Business Problem Agents often need to share a contact's details — such as a supplier, referral, or colleague — directly within a customer conversation. Currently, respond.io has no way to send a contact card (name, phone number) as a message, which is a native feature in WhatsApp. Agents must manually type out or copy-paste contact details, which is inefficient and error-prone. Desired Outcome: Allow agents to share a contact card from the respond.io Contacts list directly within an Inbox conversation, similar to WhatsApp's "Share Contact" feature. The recipient would receive a structured contact card containing the contact's name and phone number. Current Workaround Manually typing or copy-pasting contact details into the chat — no structured contact card format available.

Problem / Use case: When exporting Contacts (via Contacts module export or Workspace Settings → Data Export), there's no way to see when a Contact last read a message. This data exists today, but only at the message level inside Reports → Messages → Outgoing Message List ("Read Timestamp") — it's not surfaced anywhere in a bulk, contact-level export. Customers doing offline reporting, engagement analysis, or reconciliation need this without having to manually cross-reference the Reports module message-by-message. Proposed solution: Add a new column to the Contacts export (both the Contacts module export and the Enterprise Data Export tool) — e.g. Last Message Read At — reflecting the most recent read timestamp across a Contact's messages. Ideally align this addition across both export surfaces so they don't drift out of sync again. Known constraints to flag (so it doesn't get built and then rejected): Read receipts don't exist for all channels (e.g. no read receipts on SMS) and can be disabled by the contact (common on WhatsApp) — the column will have legitimate nulls, so it needs clear labeling/help text rather than being read as "never opened." This is a message-level fact being rolled up to a contact-level field, so a product decision is needed on which message's read time counts (most recent, across which channels).

Business Problem: Currently, users must fill in every part of an HTTP Request by hand — method, URL, headers and body — in both Workflows and AI Agent actions. Most API providers already give a ready-made cURL command, so users break it apart and retype each piece. This is slow, error-prone, and mistakes usually appear only during testing. respond.io already shows requests as cURL in the AI Agent event log, so the format is already in the product. Desired Outcome: Let users paste a cURL command and have the method, URL, headers and body filled in automatically. Any field can still be edited before saving. Use Cases: Paste a CRM's cURL example to set up an AI Agent action in one step. Move a request that already works in Postman into a Workflow without retyping it. Current Workaround: Copy the method, URL, each header and the body into the fields one by one.

Business Problem: Currently, the mobile app does not offer the option to download videos directly from the conversation. This limitation affects users who need to access video content offline for various purposes, such as reviewing customer inquiries, sharing information internally, or following up on discussions. Desired Outcome: Download & Share Videos: Enable users to download & share videos directly from conversations on the mobile app.

Business Problem: Agencies and advanced users increasingly use AI assistants (Claude, Claude Code, ChatGPT, Cursor) to build, configure, and maintain customer workspaces. Today this creates two distinct blockers: For everything the REST API covers (contacts, messages, custom fields, broadcasts), users must write custom scripts every time instead of asking the assistant directly. For everything the API does not cover (Workflows, AI Agents, Snippets, channel configuration), the work is 100% manual in the UI — no AI assistance, auditing, or automation is possible at all. For agencies managing dozens of client workspaces, this multiplies onboarding time and increases configuration errors. Desired Outcome: An official respond.io MCP (Model Context Protocol) server that allows any compatible AI assistant to connect via a standard connector and execute actions in natural language without writing code. Contact management: Search, update, tag, and move contacts across lifecycle stages via natural language. Messaging and broadcasts: Send broadcasts to tagged segments, read and summarize unanswered conversations. Snippets: Create, list, and detect duplicate or outdated snippets programmatically. Audit and diagnosis (stretch goal): Read and inspect Workflow and AI Agent configurations to assist with setup, auditing, and cross-workspace comparison. Minimum actions the MCP should expose: Read / create / update contacts, custom fields, tags, and lifecycle stages Send individual messages and broadcasts Read conversation history and internal comments Programmatically create, list, and edit Snippets (Stretch goal) Read and inspect Workflow and AI Agent configuration for auditing and setup assistance