Sixty cards in a pocket, and Monday to type them
A visiting card scanner that does not build you a phone book. It reads the card into the enquiry it belongs to — with a source, a salesman and a follow-up date already on it.
The stack that never gets typed
You come back from the exhibition with a pocket full of cards.
Every card in it belonged to somebody who stopped, talked and handed it over. Some of them meant it.
Cards in a drawerThe old way- Typed up later — and later is next month
- No source and no salesman — so nobody owns any of them
- No date on any of them — so none of them is overdue
Scanned at the stall- In the record before you leave — while you still remember the face
- Source and salesman attached — somebody owns it
- A follow-up date already on it — so it can go overdue, and be seen to
The serious one is in the stack. So is everybody else.
It reads the card into the enquiry, field by field
The enquiry module already had its fields. The scanner fills them.
Name, mobile, email, website, company name, address, city, pincode, enquiry source — these are not new fields invented for the scanner. They are the fields an enquiry has always had, which is why a scanned lead behaves like every other lead from the moment it lands.
When it puts something in the wrong box
It will, sometimes. Cards are designed by printers, not by databases.
A trading name set in the largest type gets read as the person. A designation under a name gets read as a second name. Tap the field and pick the right one from the list — the value stays, only its destination changes.
That is the whole correction. Not retyping the card: re-pointing one line of it.
The value is already read
The scanner got the text off the card. What it guessed wrong is which field it belongs in — and that is a dropdown, not a keyboard.
One tap, not one minute
A scanner that is right nine times in ten and cannot be corrected is worse than one that is right eight times and can be.
Corrected where it lands
The fix happens in the enquiry itself, by whoever took the card, while he still knows who the man was.
What it is not: a contact scanner
There are apps that turn a card into a phone contact. This is not one of them.
A card scanner- The card becomes a contact — in a phone book, with the others
- Nobody owns it — it belongs to the phone it landed on
- Nothing is due — so nothing happens
SaleShade- The card becomes an enquiry — in the list your team works from
- It carries who took it — and where it came from
- It carries a date — and turns up on that date
That is the only difference worth stating, and it is the whole difference. The card does not become a contact. It becomes something somebody has to act on.
A contact sits in a phone until somebody thinks of it. A lead sits in a list with a date on it.
The follow-up date is already set
Nobody decides it card by card at the end of a long day.
The default comes from your company settings and is configurable there, so every scanned lead arrives with a date on it. The decision was made once, in settings, by somebody who was thinking about it — not sixty times at a stall by somebody who was not.
- Set once in settings, and changeable there
- Applied to every scanned lead as it lands
- Still editable on any single enquiry
Where it earns its keep
Exhibitions
The stall is where the cards come from, and where the honest question about whether the stall paid for itself gets answered.
Visitors
A card handed over at your own counter is a walk-in with his details already printed.
Enquiry sources
Because the source is attached at capture, the scanned leads answer the same question as every other channel.
See a card scanned into your own enquiry list.
Ask for a demo