One record, many hands

A customer's story is told by many people. The seller calls, a colleague answers a question, finance sends the invoice, the Agent drafts the follow-up. When each keeps their own notes, nobody has the whole story, and the customer tells it again.

In SalexHub, everyone writes on the same record, and the record reads it back to you.

A week on one deal#

Daybook is selling to Tidewell. Dana Whitfield owns the deal.

Monday. Dana calls Maya Lindgren and logs the call on the deal with what was agreed. She asks the Agent to take it from there, and it writes three tasks on the record, each with who does it and by when.

Tuesday. Lena Ortiz in accounts takes a call from Jonas Keller about payment terms and logs it on the same deal. Priya Nair adds a note about the delivery date.

Wednesday. Dana wants to offer a discount and asks Omar Haddad on the deal itself, in a comment. Omar replies under it, the two settle the number, and Omar resolves the thread. It folds to one line: Resolved by Omar Haddad.

Thursday. Dana is back from a day off. The top of the deal's activity says what happened while she was away: Calls 1, Notes 1, Comments 2, and one conversation that waits for her reply. She asks for a summary and has the week in a paragraph, written by the Agent from the activity she can see.

Nobody forwarded anything, and Maya didn't have to explain twice.

Every conversation on the record#

Mail, calls, meetings and notes land in the record's activity, in the order they happened. A conversation that happened somewhere else is logged after the fact, and a past email can be logged too.

If your business has a kind of conversation of its own, a site visit or a demo, add it as an activity type and give it its own properties, such as who attended and what comes next. Every record can log it, and every log of it has the same fields.

What changed since you last looked#

Nobody reads a record from the top. It opens on what others did since your previous visit, counted by kind, and on the conversations waiting for your reply. A line in the stream marks where what you'd already seen begins.

Ask for a summary, and the Agent writes what happened from the activity you can see, and nothing else: what you can't see stays out of it. The summary says it was written by the Agent, and what it cost in AI credits.

Talk it through where it happened#

A question about a discount belongs on the deal, not in a chat somewhere else, where the next person won't find it. Comment on the record, reply, react, and resolve the thread once it's settled. The decision stays next to the deal it changed.

Read it the way you need#

One stream, read four ways: everything, only the conversations, only the tasks, or only the changes. Where a count is shown, it's exact: the open tasks, and every conversation on the record, not just what has loaded.

Changes sit in the same stream as the conversations that led to them. What the Agent changed is marked "via the Agent", so you can tell its work from the team's at a glance.

Why it matters more with AI#

Everything the Agent does later starts from this record. When it drafts a reply, prepares a quote or sums up a week, it reads what the team wrote here. A note Lena kept to herself is a note the Agent never sees, and a reply it drafts without it gets the payment terms wrong.

The same goes for people. When a deal changes hands, or someone is away for a week, the next person opens one record instead of five inboxes, reads what's new, and picks up where the last one stopped. The customer notices only that nobody asked them the same question twice.