Clients and contacts
Who they are, what has happened, who spoke to them last, what is open.
IceBubble CRM
Ask it about this client, this job or this survey and it answers from your own records, as you, with your own access. It drafts, you approve. It never sends, publishes or changes a setting by itself.
A sparkle button in the top bar opens a panel on the right of every page in the CRM. It knows which page you are on: open a client and "this client" means that client; open a survey template and it means that survey. Two or three buttons at the top of the panel ask the obvious questions for the page, so most days you never type.
Every person has their own chats, with a history, a new chat button, and a thumbs up or down on each answer so we can see what helped.
The same records you can see, read as you. Someone without access to a deal cannot ask about it either.
Who they are, what has happened, who spoke to them last, what is open.
The pipeline, work items, time logged, delivery plans and what is slipping.
Tickets and their history, who is booked when, who is off.
Steps, templates, audience size, and a pre-flight check before you launch.
Templates, rules and results; what a report block counts and why a record is left out.
Help written from the code. "How do I" and "why can't I" get a real answer, including which permission is in the way.
Changes go through a card that says in plain words what will happen, with an Apply button. Nothing happens until you press it, and a save that fails shows you why.
A call, a visit, a note against the client or the deal, written for you from what you said.
Move a stage, change a date, close something off. The card shows the before and after.
Describe what the brief needs and it drafts the template, or adds sections and rules to one you have. You publish.
The blocks, filters and steps laid out for you to check. Launching a campaign stays a person's click, always.
These are off the list whatever your role, so you can give it to the whole team.
The questions that used to mean a support ticket.
Why a person can or cannot use a feature, role by role, and where to fix it. Shown only to people who manage permissions.
Finds rules that can never fire, questions that hide each other, and runs a rep's answers through the template before it goes out.
Says what a block counts and which filter leaves a record out, with the real values in the field.
Steps with no template or nobody assigned, an empty audience, exits and retries that go nowhere.
Your records are read for the answer and nothing else. They are not used to train anything. The usage log keeps who asked and what it cost, never the words. You set how long chats are kept, a fair daily limit per person, and a monthly cap for the whole company, and the assistant stops politely when it is reached.
Two plans, everything else the same. The top one adds the assistant and every other AI feature in the CRM.
Anthropic's Claude, through our own account. You do not need an account of your own, and no key of yours is involved.
No. The records it reads for an answer are sent for that answer and nothing else, under a commercial agreement that rules out training.
The assistant says so and stops until the day or the month rolls over. The cap is yours to set, and we tell you before you get near it.
Yes. It is switched on per role, so your sales team can have it while the field team does not. The plan covers the whole company either way.
Same tools, same access checks. The connection is for people who already live in Claude or ChatGPT and want their CRM there. The assistant is inside the CRM, knows the page you are on, and can draft and apply changes. Both are in the With Assistant plan.
Yes. Book a demo and we switch it on for your account for a fortnight.
Half an hour on a call: we open your CRM, or ours, and you ask it whatever you like.
Prefer not to book online? Call 07766 120568 or email hello@icebubble.co.uk.