Inside Libromi Team Inbox, Gsheet CRM opens as a sidebar next to the conversation. Each time an agent switches chats, the sidebar looks up the contact’s phone number in your sheet’s phone column and shows the row it finds — name, stage, budget, notes, follow-ups, linked tables — editable in place. Move down a queue of twenty chats and the right customer appears beside each one without anyone searching.
The join is the phone number and nothing else, because it is the one identifier a WhatsApp conversation reliably has. Spreadsheets hold numbers typed by humans over years — 9876543210, 098765 43210, +91 98765-43210 — and the inbox holds them in international format, so both sides are normalised before they are compared. The app never guesses a country: a bare local number with no country configured for the workspace is left unmatched rather than assumed, because a wrong guess is how one customer’s chat lands on another customer’s row.
Three outcomes are designed for, and each has its own screen:
- One row matches — the lead is shown, and edits write to the sheet.
- No row matches — the sidebar says “Not in your sheet yet” and offers Add as a lead, with the name and phone number from the chat already filled in. The new row lands on the same board everyone else is working, and a Source column, if you have one, is stamped with the channel the lead came from. If a number is already in the sheet under another name, the app asks before creating a duplicate.
- More than one row matches — the sidebar says so and asks you to remove the duplicate in the sheet, rather than picking one at random and letting an agent edit the wrong customer.