The questions that come up in use, and the reasoning behind the answers.
A cap has fired. Some things disqualify however well a lead scores elsewhere. Open Score breakdown on the card and it names which cap and why: beyond 90 minutes of BD20 (red), turnover above £15m (red), over £7m by band or staff (amber), five or more directors (amber), outside target trades (amber), director based outside range (amber), or two amber caps together (red).
The size deduction. If the turnover band is £7m–£15m or over £15m, or enrichment estimates 50 or more staff, three points come off once and an amber cap reads Over £7m — generally too large for the practice. Such leads go to Low fit rather than Ready to invite, whatever their colour. If the turnover band is wrong, correct it under Edit details and it rescores. The staff estimate comes from enrichment and is not editable on the card; the Score breakdown says which of the two triggered it.
Because it is a worse prospect for this model. A two-director firm at £400k has the owner in the business daily, feeling the constraint personally, able to decide alone. A £9m firm with a board buys differently and slower.
The old £2m–£15m band put a £3m owner-operator and a £14m group in the same box. The split lets the score treat them differently: £2m–£7m scores two; £7m–£15m scores two less the size deduction. A lead still holding the old band keeps scoring as before and shows a prompt on the card to choose one of the two halves. The website asks the same question in the same two halves.
That lead has not had a Companies House refresh. Select it and press Refresh from CH only — no AI call, so no cost.
Yes, and you should. Edit details on the card, set the band, Save. The score recalculates and the lead is flagged field-verified, which outranks any estimate.
Deliberately. The AI is asked for facts only; the score is calculated in code from a fixed rubric. A number that moves between runs cannot be trusted or argued with.
The criterion is drive time from BD20, not county. Hull is roughly one hour fifty. Manchester, Stockport and Wigan sit inside the boundary for the same reason.
Limited companies only drops anything not on Companies House, and businesses already held are hidden and counted separately. Untick either to see everything.
It was deleted rather than parked. Deleting removes the record and with it the reference the scraper uses to recognise a business. Park instead.
Google numbers are whatever the business last verified on its listing — often an old landline or a call-tracking number, which is why they are labelled unconfirmed. Correct it on the card.
The panel lists them with the reason — almost always no Companies House match, because the trading name differs from the registered one. Correct the name or the company number under Edit details and enrich again. Changing the company number clears the old Companies House details so two companies are never mixed.
If it happens on every search, it is the Google API key: check billing, that Places API is enabled, and that any IP restriction matches the server.
Deliberately. Each shows its name and count; open the one you are working. A long page of every pool open at once buried the one that mattered.
It does now, from the card's stage menu and from the Pipeline's bulk button alike. The lead goes to the follow-up pool with a due date six months out, soonest first, and appears on Today when the date arrives.
The owner asked not to be invited again — on the website, or recorded as NFA. The lead stays on record and can be found in All leads and Lead lookup, but it sits in no pool, bulk Add to event skips it, and it cannot be added to a morning. Only changing its stage on purpose brings it back.
Card → Directors → Edit directors → Known as. Letters then open Dear Steve, lists and the ticket write list show Steve, and the registered name is kept. Search finds him by either.
So nothing changes by accident. The confirmation lists each field that is about to change, from what to what. Cancel leaves the record untouched.
| Park | Delete permanently | |
|---|---|---|
| Record | Kept | Removed, with notes and history |
| Working lists | Hidden | Gone |
| Scraper | Still recognises it | Will offer it again |
| Reversible | Yes — Restore | No |
Top of Today → Recent activity, and top of Pipeline → All leads, which sorts by most recently touched.
Because the owner is holding a printed card, and only that number can be right. A number chosen by the CRM would be a different one, and the two could never be reconciled. The roll of two thousand is there to check numbers against, not to hand them out.
The last character is worked out from the first five, so a single slip is caught. Read it off the card again. O and nought are the same, and so are I, L and one, so those are never the problem.
That number is already recorded against the business it names. Either it was recorded against the wrong lead — open that lead, click the number and clear it — or you have misread this card.
Hand over a new card and press + card on their lead. The newest card is the one in their hand and becomes the ticket reference. Earlier cards show struck through; replies on any of them still land on this lead, and the figures count the business once.
| Button | What happens |
|---|---|
| Update lead # | The reply is written to the lead holding that card: registered on the morning chosen, declined with the reason, Mini Q and question filled |
| Create lead | An enquiry with no card. A new lead to qualify |
| Dismiss | Marked dealt with; the lead is untouched. It still counts in the card strip and the figures |
| Delete | That one entry is removed entirely. For tests and mistakes; it asks first and names the entry |
No. An older Mini Q never overwrites a newer one, a later confirmation clears an earlier decline, and a comment or Mini Q already on the lead is never undone.
No. The website has already sent it. The CRM sends nothing on a confirmation, and a second one confuses people.
Sent · Opened · Outcome · Mini Q · Ticket · Attended — what has happened to their card, read live from the website. Opened carries a count; several opens and no outcome is a call worth making. Nothing on the strip changes the record.
It no longer does. Attended, Step 6 and client are milestones, stamped when first reached and kept. A guest at Diag Booked still counts as attended on that morning's figures and on the KPIs.
Editable only while the lead is at Registered. After that it is a locked record of what they said before the morning.
The reason is what makes them workable again. "Too busy in July" and "another part of country" are completely different conversations three months later.
Pipeline → No-shows → Select all → choose the next morning → Add to event. Thirty seconds.
Archive it, then delete it from the archived list. Only archived events can be deleted, so a live morning cannot go by accident.
A line is too long or empty. The red box says which; press Edit the event, fix it, come back. The venue line holds thirty characters and is never wrapped or shrunk.
Print the alignment proof on a spoiled shell at Actual size / 100%. First measure the bar: if it is under 70 mm the printer is shrinking the page — which also closes up the gaps between lines — so fix the print setting. Then read the two scales on the Reference row and press Up / Down / Left / Right by what they show. Print the proof again until both read 0.
They were confusing. The buttons use the same words the proof prints beside its scales, and the screen says where the print sits now — "2 mm left and level".
Print write list prints the reference and guest list only, for writing by hand. The shells are only ever printed from the overlay PDF.
Open their card and press Print ticket: a complete ticket on plain paper with their reference and the event details.
Each morning is its own room. An average across them hides the morning that went wrong, which is the one you need to see.
It should not: both use the same rule. If they differ, reload both — one was opened before a change.
What the percentage is a share of. Opened and confirmed are shares of cards out; Mini Q, ticket and attended of registered; Step 6 and client of attended. Registered itself counts everyone on the board by any route — card, phone or visit — so it can exceed cards out.
Lead lookup → the Archived pill → Restore, or open the card and press Restore. Everything survives archiving.
Completely. Separate databases, logins and sessions; they share only the code. Two files differ —
config.php and brand.css — and every other file uploads to both folders
unchanged.
Behind the login. They open through the Guides menu and cannot be reached by anyone without a login. They are generated outside the CRM; an edit made on the server is lost with the next replacement.
Open error_log in that instance's folder through cPanel File Manager. The last few
lines name the file and line number. It can be deleted when it gets long.
The Business Fix CRM · FAQ v8.0 · November 2026