What is a Contact?

Updated 31 May 2026·8 min read

A contact is a person you have an ongoing business relationship with — current customer, past customer, vendor, partner, referral source. This page explains what makes someone a contact, when to add one, and how to think about contacts using a real Nashik coaching-centre example.

Meet Rohan

Rohan Kulkarni runs Kulkarni Coaching Classes in Nashik. Two floors above a samosa shop on College Road, about 400 students every year, mostly Class 11 and 12 — JEE and NEET preparation. He’s been running it since 2013.

Each of those 400 students has at least one parent in the picture. Often both parents and an older sibling who already studied with Rohan’s team. Over 13 years, that adds up — about 1,200 alumni parents, 800 alumni students now in college or working, fifty school counsellors who regularly send him referrals, eight vendors (textbook supplier, AV equipment, the chai aunty downstairs who handles all student snacks), and three lenders who help parents arrange education loans.

Every one of those people is a Contact in Rohan’s TatvaCRM.

The 30-second answer

A contact is anyone your business has an ongoing relationship with — paying customers, past customers, vendors, referral partners, lenders, anyone whose name and number you need to keep, with their entire history attached. Unlike a lead (someone who might buy), a contact is someone you already know. Every person who has paid you, will pay you again, or helps you make money is a contact.

Who counts as a contact?

The strict definition is short: anyone you have a real, named business relationship with. The practical definition is broader. In Rohan’s CRM, the 1,800+ contacts split roughly like this:

Type	Rough count	Example
Current students	400	Aarav — Class 12, JEE batch, joined April 2026
Current student parents	~700	Mrs Deshmukh — Aarav’s mother, primary contact for fee payments
Alumni students	~800	Tanvi — IIT Bombay 2024 batch, occasionally sends younger cousins
Alumni parents	~1,200	Mr Joshi — son Anish was in 2018 batch, now asks about his daughter
Referral partners	~50	Sandhya Karnik — counsellor at Don Bosco school, sends 8–10 students/year
Vendors and partners	~15	Sharma Book House — supplies all reference books

All of them are contacts. None of them are leads. The thing they have in common is that Rohan’s business has a real, named relationship with them — past, present, or genuinely promising.

Lead vs Contact — the short version

A lead is a person who has shown interest but you haven’t yet confirmed they’re a fit. A contact is a person you already know, in the business sense — they’ve paid, they’ve worked with you, or they’re actively helping you make money (a vendor, a referral source).

The threshold for a lead becoming a contact is usually one of three things:

They paid you — they’re a customer now. Move them.
You qualified them seriously — they have budget, timeline, decision authority, and active intent. Even before payment, they belong on the Contact side because the relationship is now real.
They are not a customer but they help your business — vendor, referral partner, supplier. They were never a lead.

See the dedicated Lead vs Contact page for a fuller cheat-sheet.

Why keeping a clean Contact list matters

Every February, when CBSE results come out, Rohan’s team runs a re-engagement campaign. They WhatsApp every alumni parent — the 1,200 of them — with one message: “If your younger child is now in Class 9 or 10, we’d love to talk to you about our early-foundation programme.”

Out of 1,200 alumni parents, about 90 reply. Out of those 90, about 40 come in for a counselling session. Out of 40, about 25 enrol their second or third child. Twenty-five admissions × ₹85,000 = ₹21.25 Lakh of revenue every year, almost entirely from existing relationships.

That campaign is possible because Rohan’s Contact list is clean. Each alumni parent record has: which child studied with him, which batch, current college, any siblings still in school, last conversation date, last referral made.

If Rohan ran that campaign blindly from a phone-number export, he’d look amateur. Imagine messaging Mrs Kothari about “your child’s next steps” when her son passed away in 2019. The Contact record had a note. The CRM caught it. The message wasn’t sent.

Why this matters

A Contact in a CRM isn’t just a name and a number. It’s a name, a number, and the entire history of every conversation, transaction, and connection that person has with your business. That history is what turns a cold-feeling re-engagement campaign into a warm one. It is what stops you from sending the wrong message to the wrong person. It is what makes a 13-year-old coaching centre feel like a small family business even at 400 students per batch.

What lives on a Contact record?

In TatvaCRM, every contact has the basics — name, phone, email, address. Around that, the things that actually matter for Rohan’s business:

Relationship — parent of which student? Spouse of which other contact? Sibling of?
History — every fee receipt, every WhatsApp summary, every phone call note, every meeting that has ever happened with this person.
Status — current student parent / alumni parent / dropped out / never enrolled.
Owner — which counsellor is the primary point of contact for this family. Mrs Deshmukh’s queries always go to Pooja, not whoever picks up.
Tags — “JEE batch 2026”, “bulk discount applied”, “referred by Don Bosco”, “loan facility used”. Whatever lets Rohan filter later.
Custom fields you need — for Rohan: student’s target college, board (CBSE / ICSE / State), 10th-class marks, fee plan (monthly / quarterly).

A Monday morning in TatvaCRM

It’s a Monday in February. Pooja, Rohan’s senior counsellor, opens TatvaCRM at 9:30 with her tea. Her morning view shows three things:

4 contacts to call back today — promises she made last Wednesday.
2 fee renewals due this week — for current student parents.
1 birthday today — Aarav from JEE batch turns 17. (Yes, the CRM tracks this. Yes, parents notice.)

Pooja calls Mrs Deshmukh. Aarav’s mother. She’s called Mrs Deshmukh probably twenty times over the last fourteen months, and every previous conversation is right there on screen — last September’s conversation about Aarav’s low mock test scores, the December meeting about whether to drop dropper-year prep, the January note that the family is also looking at a centre in Pune for a backup.

When the call connects, Pooja doesn’t ask Mrs Deshmukh how Aarav is doing in JEE prep. She asks: “How did Aarav handle the FIITJEE mock he took on Sunday? He was worried about the maths section last week.” Mrs Deshmukh is, frankly, delighted. Three minutes of conversation later, the fee renewal she was on the fence about is confirmed.

Two years ago, before TatvaCRM, Pooja was juggling sticky notes and four WhatsApp groups. She didn’t know which Aarav. She didn’t know which mock. She opened every call with “Sorry ma’am, can you remind me which batch?”The week she lost a renewal because she couldn’t remember a student’s name was the week Rohan signed up for TatvaCRM.

Common confusions, cleared up

“Someone I’m sure will buy next month — Contact or Lead?”

Contact. If you’re confident enough to bet on it, treat it like it’s already happening. Move them to Contact, create a Deal for the expected sale with a close date in the future, and work it from there. The Lead bucket is for unproven interest. A confident prediction is past that point.

“A customer hasn’t bought anything from us in three years. Still a Contact?”

Yes — but mark them as dormant. Dormant contacts stay in the CRM for re-engagement campaigns (like Rohan’s alumni parents). They shouldn’t appear in your active customer count. The day they buy again, you flip the status back to active and the history is all still there.

“The parent is the customer, but the child uses the service. Who do I add?”

Both — as two separate contacts linked to each other. Rohan adds the student as a Contact (they’re who the classes are actually delivered to) and the parent as a separate Contact (they’re who pays). The two contacts link to the same Family record — TatvaCRM lets you add custom relationships like “parent of” and “child of.” Same logic works for an HR head being your contact but the actual product users being someone else.

“Our chai vendor — Contact?”

Yes, technically. If you ever order from them and need to track payments or renewals, add them with a tag like “Vendor.” But honestly, most coaching centres don’t need their chai supplier in the CRM. Use judgement — if you’d be in trouble when the relationship breaks, they belong here. If they’re truly fungible, don’t.

“A customer passed away. What do I do with the record?”

Don’t delete it. Mark the contact as deceased with a date — TatvaCRM has a specific status for this. The reason matters: deletion makes the rest of your history confusing (their child’s record, their referral history, their past conversations all become orphaned). Marking them deceased keeps the history whole while ensuring no one accidentally messages them or their family in a re-engagement campaign.

“Same person, different phone numbers from different times. One Contact or two?”

One. Merge them. Keep both phone numbers on the merged record — TatvaCRM supports multiple phones per contact. The history from both records combines. This happens constantly with parents who change phones, who add a second WhatsApp number, who hand the phone to the spouse for one call. Don’t let it fragment your customer history.