Guide
How to turn screenshots, badges and email signatures into CRM contacts
By Lev Perlman5 min read
A screenshot of a profile holds most of what a CRM record needs, and it takes two seconds. Send it to Shmor with a line of context, and it reads the name, job title, company and any contact details, then saves the person and company to ShmorCRM, Attio or HubSpot with a note and a follow-up task.
This guide covers the screenshots that work best, how to take them, and what to add so the record is useful later. For paper business cards, see getting a business card into your CRM.
What you can send
| Source | What it usually shows | Tip |
|---|---|---|
| LinkedIn profile | Name, headline, current company, location, profile URL | Capture the top card, with the name and headline |
| Event-app profile | Name, job title, company, sometimes email or LinkedIn | Open the full profile, not the attendee list |
| Conference badge | Name, company, sometimes job title | Photograph it straight on, without glare from the plastic sleeve |
| Email signature | Name, title, company, phone, email, website | Forwarding the whole email is often better (below) |
| Website team or contact page | Name, role, sometimes email | Crop to one person |
Step 1: take a clean screenshot
A good screenshot is one Shmor can read without guessing:
- One person per image. An attendee list with twenty faces gives Shmor nothing to choose between.
- Include the name and the company. Those two, or an email address, are what a record is built on. If the company is further down the profile, scroll so both are in view, or take a second screenshot.
- Crop out the noise. Adverts, "People also viewed" panels and suggested connections are ignored, but cropping them out removes any doubt.
- For badges and cards, use light and an angle. Tilt slightly to avoid reflection on laminated badges.
Shmor reads what is visible. It does not open links in the image or look anyone up, so if the email address is not on screen, it will not be in the record. The exception is a LinkedIn link you paste as text, which Shmor can look up with your own Apollo key: see LinkedIn lookups with Apollo.
Step 2: add a caption with the context
A screenshot tells Shmor who someone is. Only you know why they matter. Before you send, add a caption covering how you met, what you talked about and the next step:
Met at the Leeds SaaS meetup. Runs RevOps, unhappy with their current CRM data. Send the hygiene checklist on Monday.
Shmor turns that into the note on the person, sets Met via and Met at, and creates the follow-up task. If you send the screenshot with no caption, the person is still saved, and Shmor's reply asks how you met and whether to follow up.
You can also add the context afterwards, by text or voice note, as a reply to Shmor's card.
Step 3: send it
On Telegram
In the Shmor chat, tap the attachment icon, choose the screenshot, type the caption and send. One image per message. Images up to 10 MB are accepted.
By email
Attach the screenshot to an email to in@emails.useshmor.com from your Shmor sign-in address, with the context in the body. By email you can attach up to 5 images about the same person, for example the top of a LinkedIn profile and the contact details further down. Tiny images, such as logos, are skipped.
Email signatures: forward, do not screenshot
If the signature is in an email you received, forward the whole email to in@emails.useshmor.com instead of screenshotting it. Shmor reads the body, including the forwarded message and its signature, and the email gives it the sender's address as well. Add your line of context above the forwarded message. The email forwarding guide has the details.
Step 4: check the reply
Shmor replies with New contact saved or Existing contact updated, the person and company, where you met and the follow-up date. It extracts:
- person: first and last name, job title, email addresses, phone numbers (in international format when the country is clear), LinkedIn URL and location;
- company: name, and web domain only if it is shown or can be taken from a work email address. A Gmail or Outlook address is never used as a company domain.
If a detail is wrong, reply to the card: "the company is Northwind Analytics, not Northwind" or "her name is Amara Okafor". To rename someone, give both first and last name.
If the image has no name, email or LinkedIn link that Shmor can read, it replies that it could not find a person, and no capture is used.
Common problems and fixes
- The company is missing. Many LinkedIn headlines say what someone does rather than where. Add the company in your caption: "works at Northwind".
- The wrong job title. Profiles can list several roles. Shmor takes the current one where it can tell; correct it by reply if not.
- A badge with only a first name. Add the surname and company in your caption, or reply later once you have connected online.
- An event app that hides contact details. Save the person now with name and company; add the email when they reply to your follow-up.
Duplicates are handled for you
If you screenshot someone who is already in your CRM, Shmor finds them by email, then LinkedIn URL, then name and company, and updates the existing record with anything new. Met via and Met at are set only if empty, so the first meeting is kept, and your new note and task are added to the same person.
A note on the people in your screenshots
Screenshots are read by OpenAI on Shmor's behalf and are not stored by Shmor; OpenAI does not use API data to train its models by default.1 Saving the details of someone you met so you can follow up is normal business practice, and legitimate interests is the lawful basis businesses commonly rely on for it in the UK.2 Capture what you need for that purpose, and leave out the rest.
Sources
-
OpenAI, Data controls in the OpenAI platform. ↩
-
Information Commissioner's Office, Legitimate interests. ↩