Find the customer texts that never made it into your CRM

Build me an internal app my team opens once a week to reconcile our customer text conversations against HubSpot. The problem it solves is that half our relationship history lives in text threads nobody else at the company can see. The people who use it are our sales lead and the reps who do the texting, and the object they work is an unfiled conversation, not an unanswered one, so this is a periodic hygiene pass rather than a live inbox.

Main view. One board listing every Linq conversation with activity in the window, defaulting to the last 14 days. Load conversations with Linq List Chats and, for each one, the recent messages with Linq List Messages. Linq list endpoints paginate with a cursor and a limit that defaults to 50 and maxes at 100, so page until the cursor is exhausted, and cache what you fetch in the app's own storage so the board opens fast instead of refetching everything on every visit. Split the rows into three buckets shown as tabs or sections: matched to a HubSpot contact and already filed, matched to a contact but never filed, and unknown numbers with no CRM record at all.

Matching. Linq handles are E.164 phone numbers or email addresses. For each conversation take the customer handle and look the person up with HubSpot Search Contacts against the phone, mobile phone and email properties. Normalize the number and try a few sensible variants so a contact stored as (555) 123-4567 still matches a handle of +15551234567. Cache the resolved contact id per handle in the app's storage so a later pass does not re-search every thread from scratch.

Filed state lives in the app. Keep a record of every filing: the chat id, the contact id, the timestamp of the last message covered by that filing, and a reference to the note that was posted. Never file the same thread twice. If new messages have arrived since the last filing, show the row as having new activity since it was last filed and offer to file only the new stretch of the conversation rather than the whole thing again.

Every row shows the customer name, or just the number when there is no record, the channel the thread ran on (iMessage, RCS or SMS, since a conversation can span all three), the time and a short preview of the last message, how many messages are in the window, the filed state, and that contact's open deals with amounts from HubSpot Search Deals. Default sort is unfiled conversations first, ordered by the total open deal value sitting behind them, so a thread attached to live pipeline outranks one with somebody we already lost. Let the user change the date window and switch the sort to most recent or longest unfiled.

Summarize and file, powered by a background agent inside the app. On a matched but unfiled row there is a Summarize and file button that kicks off an agent. The agent reads the whole conversation with Linq List Messages, paging until it has the full history, then writes a short factual summary of what was discussed: the commitments made on either side, any dates that were agreed, and the next step. It summarizes rather than transcribes, and it should read like a rep wrote it, plain and specific, with no marketing language and nothing invented that is not in the messages. The summary comes back into the app and is shown to the user in an editable box.

When the user approves the text, the app posts it to the contact's timeline with HubSpot Create Note associated with that contact, and stamps a last texted date on the record with HubSpot Update Contact. Nothing is posted until the user has seen and approved it, and the edit box is never skipped. After a successful post, record the filing in the app's storage, move the row into the filed bucket, and show a link through to the note.

Unknown numbers. On an unknown number row the user can create the person first with HubSpot Create Contact, using a small form pre-filled with whatever the thread reveals, such as a name mentioned in the messages and the phone number itself. Once created, the same summarize and file flow runs against the new contact. Use HubSpot Get Contact to back a detail panel when someone wants to look at the full record before filing anything against it.

Inline actions. From any row the user can fire off a quick reply with Linq Send Message and mark the thread handled with Linq Mark Chat Read, without opening another tool. A reply sent from the board should appear straight away in that row's message list.

Suppression list. The app keeps a list of internal and personal numbers in its own storage, and a suppressed handle never appears in any of the three buckets. Let the user suppress a number straight from a row and manage the whole list from a settings view, including removing one again.