Qué construimos después.
Proponé ideas, votá las que necesitás y seguí su estado. Lo más votado sube en la lista.
- 0
Chat: Sort the inbox by newest, oldest or longest wait
Intercom lets the team sort the inbox by Waiting since, ascending, so the visitor who has waited longest comes first (https://www.intercom.com/help/en/articles/6989006-inbox-sorting). Our inbox was fixed to latest activity (lib/chat-data.ts). A small team with no SLA policy had no way to see who was overdue. Built: a Sort select in the inbox with newest, oldest and waiting longest, where waiting counts from the visitor's first message after the last human or bot reply and ignores internal notes.
Chat: Combine priority and waiting time in one inbox sort
Intercom users ask for sorting that puts urgent conversations first and then the longest waiting, because the two sorts cannot be combined today (https://community.intercom.com/ideas/combined-sorting-for-priority-and-non-priority-conversations-13151). Our inbox now sorts by newest, oldest or waiting longest (lib/chat-data.ts conversationOrderBy) but priority is only a filter. First scope: a fourth sort option, Priority then waiting, ordering urgent, high, medium and low and breaking ties by waiting since.
Chat: Show how long each visitor has been waiting in the inbox rows
Intercom shows a waiting-since time on each conversation row so the team sees at a glance who is overdue (https://www.intercom.com/help/en/articles/6989006-inbox-sorting). Our rows in components/chat/ConversationList.tsx show the last message and SLA badges only when a policy exists, so a team without SLA policies cannot see who waits longest. First scope: a short relative label such as 12m or 3h on rows where the last message is from the visitor, computed from the same waiting-since rule used for the Waiting longest sort.
Chat: Schedule an agent reply to send later
Intercom lets teammates schedule a message to go out at a chosen time, useful when replying across time zones (Intercom help center, inbox composer). Our composer in components/chat/ConversationClient.tsx only sends immediately or saves an internal note. A team in Buenos Aires answering a visitor in Madrid ends up writing at the wrong hour or forgetting the reply. First scope: a Send later option with a date and time, a pending row in the conversation that can be edited or cancelled, and delivery from the minute cron with a compare-and-set claim.
Chat: Show expected reply time in the widget header
Intercom's Messenger can show a reply time expectation such as a few minutes or a day (Intercom help center, Messenger settings). Our widget (app/api/chat/widget.js/route.ts) shows office hours state but never says how long a visitor should wait. Visitors who write outside the first minutes assume nobody is there and leave. First scope: a per-widget choice among a few fixed options in WidgetSettings, rendered under the widget title in en/es/pt, and hidden when the team is away per office hours.
Chat: Block a visitor or mark a conversation as spam from the inbox
Intercom lets teammates mark a conversation as spam and block the sender so they stop reaching the inbox (Intercom help center, Inbox section). Our inbox has no way to ban a visitor: lib/chat-data.ts and app/api/chat/messages/route.ts accept messages from any visitor key and the only recourse is resolving each conversation. A small team on a public widget gets junk quickly and has nobody to filter it. First scope: a blocked flag on chat_visitors, a Block action in the visitor panel, new messages from that visitor dropped silently by the widget endpoint, and a list of blocked visitors in widget settings with unblock.
Chat: Replace 3-second full polling with incremental fetches
ConversationClient.tsx:280-291 polls the full message list, typing status and the conversation every 3 s (about 60 requests per minute per open tab). InboxShell.tsx:139-171 polls conversations every 10 s. listChatConversations (lib/chat-data.ts:911-928) runs 2-3 correlated subqueries per row. On Turso, every open tab is constant load. Intercom pushes updates over a socket. First scope: add ?since=<updated_at> so only new messages are fetched, pause polling while document.hidden, and denormalize last_message_body onto chat_conversations. Priority: medium. Effort: M.
- 0
Chat: Find conversations and people from Cmd+K
Cmd+K (lib/app-search.ts) finds chat widgets but not conversations or visitors, so finding 'the customer from yesterday' means opening the inbox and switching the status filter. Intercom search covers conversations, people and messages. First scope: add chat visitors (name, email) and conversations (subject, last message, visitor) to the palette with status and age as meta, linking to /app/chat/inbox/<id> and /app/chat/people/<id>, scoped to the widgets the user can access.
- 0
Chat: Save inbox filters as views in the sidebar
Intercom turned saved searches into sidebar Views in October 2026 (https://www.intercom.com/changes/en/page/1). Our inbox (components/chat/InboxShell.tsx) has status, assignee, tag and text filters but they reset on each visit, so 'urgent + billing tag + unassigned' has to be rebuilt every time. First scope: save the current filter set with a name, list views under Inbox in the Chat sidebar with live counts, share a view with the team or keep it private, and reorder or delete views.
- 0
Chat: Report bot deflection, tags, busiest hours and SLA compliance
Intercom reports Fin and humans together with response times, ratings and SLA metrics, plus custom reports on higher plans (https://www.intercom.com/pricing). Our Reports page (getChatRangeReport in lib/chat-inbox.ts) shows conversations, first response, resolution and CSAT per agent; a conversation answered by the bot shows a dash in first response and there is no bot resolution rate. First scope: bot-resolved vs handed-off counts, conversations by tag and by widget, a weekday by hour heatmap of new conversations, and percent within SLA for first response and resolution, all with the same date range and CSV.
Chat: Create or link a Track issue from a conversation and reply to all when it ships
Intercom has back-office and tracker tickets: one ticket groups many conversations and a note can be posted to all of them at once (https://www.intercom.com/help/en/articles/6436600-tickets-explained, https://intercom.com/help/en/articles/8300306-how-to-manage-tracker-tickets). Track is in the same suite but a human agent cannot file a bug from the conversation (only the AI agent can, with track_create_issue). First scope: 'Create issue' and 'Link issue' in the conversation panel with the title prefilled from the last visitor message and a transcript link, a linked-conversations list on the issue, and when the issue moves to Done a one-click reply to every linked open conversation.
- 0
Chat: Fill variables like {{name}} and {{email}} in saved replies and macros
Intercom macros insert attributes such as first name and company. Our saved replies (components/chat/CannedClient.tsx) are inserted literally: a reply with {{name}} reached the visitor as '{{name}}' in the benchmark walk, and the keyword bot sends canned bodies as they are. First scope: support {{name}}, {{first_name}}, {{email}}, {{agent_name}} and custom conversation attributes with a fallback ({{name|there}}), a variable picker in the canned editor, substitution on insert in the composer and in the bot path, and a preview.
- 0
Chat: Show who is viewing or replying to a conversation to avoid double answers
Intercom shows when a teammate is viewing or typing in the same conversation; without it two agents answer the same customer. We already track typing for the visitor side (app/api/chat/conversations/[id]/typing) but agents never see each other. First scope: record agent presence per conversation on the existing 3 s poll, show avatars of other agents viewing and an 'Ana is replying' line above the composer, and warn before sending if another agent replied in the last minute.
- 0
Chat: Add teams with their own inbox, round-robin and assignment rules
Intercom has team inboxes, round robin per team and skill-based routing (https://www.intercom.com/helpdesk, https://www.intercom.com/changes/en/page/1); Crisp has sub-inboxes from Essentials (https://crisp.chat/en/pricing/). Our assignment rules (app/api/chat/rules) and the conversation header only assign to a person, so a team of four cannot split Support and Sales or route billing questions to one group. First scope: chat teams (name, members), assign a conversation to a team and optionally a person, an inbox filter per team, rules that target a team with round-robin among its available members, and team in reports and webhooks.
- 0
Chat: Notify agents on their phone with an installable PWA and Web Push
Intercom and Crisp ship iOS and Android teammate apps with push, and Crisp added Mac and Windows apps in 2026 (https://crisp.chat/en/blog/march-2026-product-update/). zerosoft has no service worker or Web Push, so an agent away from the desk never learns about a new chat until they reopen the tab; the inbox at 390px already works (tested). First scope: a web app manifest and service worker for /app, an opt-in for push in Chat settings, push on new conversation, on a visitor reply to a conversation assigned to me and on @mention, with a deep link to /app/chat/inbox/<id> and per-user quiet hours.
- 0
Chat: Send proactive messages by page URL, time on page or returning visitor
Intercom includes proactive chats, banners and tooltips on every plan (https://www.intercom.com/pricing) and Crisp has chat triggers from the Mini plan (https://crisp.chat/en/pricing/). Our widget only opens when the visitor clicks the launcher; the widget already knows the page URL and referrer (lib/chat-visitor-context.ts) but no rule uses them. A pricing-page nudge is how small teams turn chat into sales. First scope: per-widget auto messages with conditions (URL contains, seconds on page, first or returning visit, office hours only), a message body and optional sender, shown as an unread bubble without creating a conversation until the visitor answers, with a per-visitor frequency cap and sent/replied counts.
Chat: Add WhatsApp and Instagram as channels in the shared inbox
Intercom routes chat, email, WhatsApp, Instagram, Facebook and SMS into one inbox (https://www.intercom.com/helpdesk) and Crisp includes WhatsApp, Instagram, SMS, Line and Viber from its $95/month Essentials plan (https://crisp.chat/en/pricing/). Chat only has the web widget (app/api/chat/widget.js); conversations, visitors and rules in lib/chat-data.ts assume a widget. For teams in LatAm WhatsApp is the main support channel, so this is the first thing they ask after switching. First scope: a WhatsApp Business Cloud connection per workspace (webhook in, Graph API out) that creates chat_conversations with a channel column, shows a channel icon in the inbox rows, sends agent replies back respecting the 24 h window, and reuses assignment rules, SLA, tags and the AI bot. Instagram DMs as a second step over the same channel abstraction.
- 0
Chat: Export conversation transcripts and email a transcript to the visitor
Intercom added bulk export of conversations as PDF or plain text from the actions menu in June 2026 (https://www.intercom.com/changes/en/page/1), and Crisp and Chatwoot let agents send the transcript to the customer by email. We export only aggregate report rows as CSV (chatReportToCsv in lib/chat-inbox.ts); a single thread can only be copied by hand or logged to the CRM. Teams need transcripts for refunds, disputes and handing context to someone outside the tool. First scope: 'Download transcript' (text) in the conversation menu, an 'Email transcript' action to the visitor's email, and a CSV of messages in the reports export. Priority: low. Effort: S. Compared with Intercom.
- 0
Chat: Allow editing and deleting internal notes and agent messages
Intercom made internal notes editable by their author in March 2026, behind a 'Can edit notes' permission (https://www.intercom.com/changes/en/page/1). Our messages route app/api/chat/conversations/[id]/messages/route.ts only implements GET and POST, so a note with a wrong @mention, a typo in a reply or a pasted secret stays forever. First scope: PATCH and DELETE for the author's own notes (and agent replies not yet read by the visitor), with an 'edited' marker, and re-evaluate mentions on edit. Priority: low. Effort: S. Compared with Intercom.
- 0
Chat: Add AI compose tools for agents: summarize to note, rephrase, translate
Intercom's inbox AI lets teammates expand shorthand, change tone, fix grammar and translate a reply (Cmd+J), and summarize a conversation into an editable internal note (https://www.intercom.com/help/en/articles/6955446-fin-ai-for-help-desk). We already call the AI Gateway for the visitor-facing bot in lib/chat-bot-ai.ts, but the agent composer in components/chat/ConversationClient.tsx has no AI actions. This is agent assist, separate from the backlog items for a docs-answering bot and action-taking agents. First scope: a composer menu with 'Rephrase', 'Translate to visitor language' and 'Summarize to note', billed through the existing usage metering and hidden when AI_GATEWAY_API_KEY is absent. Priority: low. Effort: M. Compared with Intercom.
- 0
Chat: Push new messages in real time and add browser notifications with sound
Intercom's inbox and Messenger update instantly and teammates get desktop notifications for new conversations and replies. Our inbox refreshes on a 10 s setInterval only while the tab is visible (components/chat/InboxShell.tsx) and the widget polls every 5 s (app/api/chat/widget.js/route.ts); there is no browser Notification or sound anywhere in components/chat, so an agent working in another tab only sees the in-app notification bell. Live chat lives or dies on reply speed in the first minute, and hidden-tab polling makes the team miss it. First scope: browser notifications plus an optional sound for new conversations and replies to assigned chats, and keep polling in hidden tabs at a slower rate; move to SSE later. Priority: medium. Effort: M. Compared with Intercom.
- 0
Chat: Merge duplicate conversations from the same visitor into one thread
Intercom offers 'Merge into' inside a conversation to combine duplicates, and users are now asking for bulk merge (https://community.intercom.com/ideas/bulk-merge-conversations-from-inbox-multi-select-14762). We have no merge: a visitor who writes again after resolve, or from the pre-chat form and a later upload, ends up with separate conversations, each with its own SLA timer and assignee (lib/chat-data.ts createChatConversation). Duplicates inflate SLA breaches and split context across teammates. First scope: a 'Merge into…' action in the conversation header limited to conversations of the same visitor, moving messages, notes and tags into the target and resolving the source with a system message. Priority: medium. Effort: S. Compared with Intercom.
- 0
Chat: Add custom conversation attributes and require them before resolving
Intercom lets admins define conversation data attributes (e.g. topic, product area) and mark some as required before a teammate can close, which keeps reporting consistent (https://www.intercom.com/changes/en/2156-categorize-conversations-consistently-with-required-conversation-data-attributes-and-more). We only have free-form tags (lib/chat-inbox.ts) and the fixed columns of chat_conversations; reports in lib/chat-inbox.ts cannot answer 'how many billing questions this month' reliably because tags are optional and unstructured. First scope: per-widget list or text attributes edited in the conversation details panel, an optional 'required to resolve' flag enforced in PATCH, and a breakdown by attribute in reports. Priority: medium. Effort: M. Compared with Intercom.
- 0
Chat: Expose a public REST API and webhooks for replies, assignment and resolve
Intercom's REST API covers conversations (list, search, reply, assign, close, snooze, tag, notes), contacts and tags (https://developers.intercom.com/docs/references/rest-api/api.intercom.io/conversations), and Chatwoot exposes an equivalent open API. Our public API in app/api/v1 has agents, calendar, crm and links but no chat, and emitEvent is only called in lib/chat-visitor-message.ts for conversation.created and message.received; agent replies, assignment changes and resolve emit nothing. Developers self-hosting the suite (persona 2 in PRODUCT.md) expect to pipe chats into Slack, Flow or their own tools. First scope: GET/POST /api/v1/chat/conversations and messages with API keys, plus message.sent, conversation.assigned and conversation.resolved events, documented in openapi.json. Priority: medium. Effort: M. Compared with Intercom.
- 0
Chat: Let visitors see past conversations and unify visitors across devices
Intercom's Messenger home and, since June 2026, the Customer Portal list a customer's past conversations with status and search (https://www.intercom.com/changes/en/page/1). Our widget only loads the latest open/pending/snoozed conversation via getOpenConversationByVisitor in lib/chat-data.ts; once resolved, the thread disappears for the visitor and the next message starts a blank conversation. Visitors are keyed by a random localStorage id, so the same person on a phone and a laptop becomes two People with split history. First scope: a 'Previous conversations' list in the widget (read only, last 10), and for verified identities (see identity gap) attach new devices to the existing visitor record by email. Priority: medium. Effort: M. Compared with Intercom.
- 0
Chat: Show page URL, referrer, browser, language and form answers in visitor panel
Intercom shows the last page a visitor viewed when replying and offers a Recent page views sidebar app with up to 20 visits (https://www.intercom.com/help/en/articles/9277565-recent-page-views-app). Our widget sends no page context: app/api/chat/widget.js/route.ts never reads location.href, document.referrer, navigator.language or timezone, and components/chat/VisitorPanel.tsx only shows name, email, first seen, started, subject and CSAT, even though pre-chat answers are stored in visitor metadata.form. Knowing the visitor is on the pricing page or checkout changes the answer and saves a round of questions. First scope: send url, title, referrer, language, timezone and user agent with each visitor message, store them on the message or visitor metadata, and render them plus the form answers in the visitor panel. Also avoid using the raw external_id as the sender name in the agent notification for anonymous visitors (lib/chat-visitor-message.ts). Priority: medium. Effort: S. Compared with Intercom.
- 0
Chat: Bulk select conversations in the inbox to assign, tag, snooze or resolve
Intercom's Inbox has checkboxes and an action bar to bulk assign, close, snooze, tag and set priority, including from search results (https://www.intercom.com/help/en/articles/6274899-get-started-with-intercom-inbox). Our inbox list in components/chat/ConversationList.tsx and components/chat/InboxShell.tsx has no selection, and PATCH /api/chat/conversations/[id] works on one conversation at a time. After a spam wave, an outage or a Monday backlog, closing or reassigning 30 chats one by one is the most tedious part of the job. First scope: shift-click/checkbox selection, x/Shift+x shortcuts, and a bar with resolve, assign, tag and snooze backed by one bulk endpoint. Priority: medium. Effort: M. Compared with Intercom.
- 0
Chat: Add agent away status that skips round-robin and optionally reassigns
Intercom teammates set an Away status; round robin excludes away teammates and 'away and reassign' sends their open conversations back to the team inbox, and the June 2026 changelog added availability filters (https://www.intercom.com/help/en/articles/6512504-round-robin-deep-dive, https://www.intercom.com/help/en/articles/6522874-manage-teammate-status-in-the-next-gen-inbox). Chatwoot has Online/Busy/Offline plus auto-offline. Our applyAssignmentRules in lib/chat-data.ts sorts all workspace agents by active load with no notion of availability, so a teammate on vacation keeps receiving new chats that breach SLA. First scope: an Away toggle in the inbox header (stored per user), round-robin skips away agents, and an option to unassign their open conversations when going away; reuse the CRM lead-assignment out-of-office flag if possible. Priority: high. Effort: M. Compared with Intercom.
- 0
Chat: Search inbox by message content, not only subject, name and email
Intercom Inbox search matches conversations containing the query words and combines with tag, user, assignee and date filters, sorted by relevancy or date (https://www.intercom.com/changes/en/2285-find-the-exact-conversations-you-re-looking-for-with-flexible-search-and-filters-for-inbox). Our listChatConversations in lib/chat-data.ts only applies LIKE to c.subject, v.name and v.email, so searching for an order number, error text or a phrase the customer wrote returns nothing. Finding 'the person who asked about X last week' is a daily support task. First scope: add an EXISTS match on chat_messages.body (including notes for agents) with a snippet of the matching message in the list row, then an FTS index if volume needs it. Priority: high. Effort: S. Compared with Intercom.
- 0
Chat: Localize the embedded widget UI (en/es/pt) instead of hardcoded English
Intercom localizes all Messenger UI to the visitor's browser language for every supported language, with a language_override attribute (https://www.intercom.com/help/en/articles/180-localize-the-messenger-to-work-with-multiple-languages). Our widget script hardcodes English strings such as 'Type a message…', 'Start chat', 'We're away right now.', 'How would you rate your experience?', 'Search articles…' and the default welcome 'Hi there. How can we help?' in app/api/chat/widget.js/route.ts. This breaks PRODUCT.md's rule of no hardcoded UI strings across en/es/pt, and Latin America is the home market, so most end customers see an English widget on a Spanish site. First scope: move widget strings to the chat messages namespace, pick the locale from navigator.language or a data-locale attribute, and add a widget-level default language setting. Priority: high. Effort: S. Compared with Intercom.
- 0
Chat: Email unread agent replies to offline visitors and thread email replies back
Intercom delivers an inbox reply by email when the customer has not seen it in the Messenger within a few minutes, and Chatwoot's conversation continuity threads the customer's email reply back into the same chat (https://community.intercom.com/questions/6536, https://chatwoot.com/docs/product/channels/live-chat/conversation-continuity). Today an agent reply is only stored and shown on the next widget poll: app/api/chat/conversations/[id]/messages/route.ts sends no email, and lib/chat-visitor-message.ts only notifies agents. For a small team that answers hours later, the visitor has usually left the page, so the reply is never read. First scope: if a visitor with an email has not read an agent message (read_at null) after 5 minutes, send one email with the reply and a link that reopens the widget; then add inbound reply-by-email via a per-conversation reply-to address. Priority: high. Effort: M. Compared with Intercom.
- 0
Chat: AI bot that answers from your public docs
Answers every visitor message until a teammate replies, and hands off when unsure.