I have set up Close CRM for a handful of different teams over the past few years, and every time I open a fresh instance the experience is the same: the defaults are technically functional, but practically wrong. Generic lead statuses that don't map to how anyone sells. No smart views. Sequence templates written for a hypothetical prospect who doesn't exist. Reps land in the tool, poke around for a week, and start building workarounds instead of pipelines. By month two, the CRM is a mess and nobody trusts the data.
The fix is not complicated. It's a one-afternoon configuration pass before anyone else logs in. Here is exactly what I do.
Start With Lead Statuses
Close ships with statuses like "Potential," "Open," "Contacting," "Unqualified," "Interested," and a handful of others. These are fine as concepts, but they describe an abstract pipeline, not an actual sales motion. The first thing I do is rewrite them to match what the team actually does.
For a typical outbound SDR setup, I replace the defaults with:
- New (lead imported, not yet touched)
- Active Cadence (a sequence is running)
- No Reply (sequence ran to completion, no response)
- Responded (any reply received, next step is qualification)
- Qualified (had a conversation, confirmed fit criteria)
- Meeting Set (a call or demo is booked)
- Not a Fit (qualified out, leave visible for future reference)
- Won and Lost (opportunity outcomes)
The logic here matters as much as the labels. Status is the rep's answer to "where is this lead in my pipeline?" If the statuses don't match the actual stages of your process, every pipeline review becomes a conversation about what a word means rather than what a deal needs. Get it wrong once and you will spend months trying to retroactively clean it up.
Close lets you define statuses per pipeline. If the team runs both outbound and inbound motions, build separate pipelines with separate status sets rather than trying to squeeze both into one.
Build Three Smart Views Before the First Rep Logs In
Smart views are saved searches that update in real time as records change. They are the best feature in Close and the one most teams underuse. The three I always build first:
1. No Touch in 3 Days. Filter: leads in "Active Cadence" status where the last activity date is more than 3 days ago. This surfaces sequences that have quietly stalled. Without this view, a rep can easily have 15 leads sitting in "Active Cadence" with nothing actually running. The view makes the problem visible in one click.
2. Qualified, No Next Step. Filter: leads in "Qualified" status with no open task and no upcoming event. These are the deals most likely to slip. Someone had a good conversation, marked the lead qualified, and then didn't book the next action. This view is the safety net for that moment.
3. My Open Tasks Today. Filter: tasks assigned to current user, due today or overdue. Pin this to the sidebar as the rep's default landing view. It replaces the habit of checking email to figure out what to do next. Everything that needs attention is in one place.
Name them clearly, pin them to the sidebar in the right order (Today's Tasks first, then No Touch, then Qualified No Next Step), and walk through how to use them in the team onboarding session. A view nobody knows about is just a view that doesn't exist.
Set Up One Starter Sequence
Most reps run email sequences manually because the built-in defaults don't match how they talk. Rather than leaving them to build from scratch, I drop in one opinionated starter sequence before go-live. The goal is not perfection. It is giving people a starting point they can customize instead of a blank screen that paralyzes them.
The structure I use:
- Day 1: First touch. Short intro, one sentence on why you're reaching out to this specific person, one sentence on what you do. Three to four lines total. No attached deck.
- Day 3: Follow-up. Reference the first email directly. One specific value line relevant to their context. Keep it shorter than the first.
- Day 7: Value drop. Share something genuinely useful: a brief insight, a relevant resource, a question that makes them think. Not a pitch.
- Day 10: Phone task. If a phone number is on the record, this triggers a task to call. The rep decides how to handle it; the system just surfaces the signal.
- Day 14: Breakup email. Two sentences. Honest, direct, easy to reply to. "I'll stop reaching out after this. If the timing is ever right, here's how to find me."
Everything in this sequence is a template, not a script. Flag it clearly in the template name ("Starter Outbound v1 - customize before using") so reps understand it's a scaffold, not a finished product.
Add Four Custom Fields
Close lets you add custom fields to contacts, leads, and opportunities. The defaults give you name, company, email, phone. That is not enough to run a real pipeline review. The four I always add:
- Lead Source (dropdown: inbound, outbound, referral, event, partner). This tells you, months later, where your best leads actually came from. Without it you are guessing at channel performance.
- ICP Score (dropdown: High / Medium / Low, set manually during qualification). Gives the team a shared language for prioritization. Reps stop arguing about which leads to focus on because the score is explicit.
- Decision Maker Name (text). The lead contact is often a gatekeeper, not the buyer. This field captures the name of the actual person who signs off, so it doesn't live only in someone's email or memory.
- Last Pipeline Review Date (date). Updated during each weekly or bi-weekly pipeline call. Lets you filter for deals that haven't been touched in a review cycle, which is usually the first sign something is slipping.
Four fields. Add more and they stop getting filled in. The discipline is to only add a field if someone will actually update it and someone will actually use it in a decision.
Configure Activity Notifications (Then Turn the Rest Off)
Close has a broad notification system that most teams leave at the defaults, which means everyone is getting alerts for everything and ignoring most of them. The ones worth keeping on:
- Email opened: tells the rep when a prospect reads their email. Useful for timing a follow-up call. Not an excuse to call every time an email gets opened, but good signal for warm timing.
- Missed call to lead owner: delivered by email. Closes the loop so a rep knows a prospect called back and they missed it.
- Lead assigned: instant notification when a new lead lands in a rep's queue. Removes the lag between assignment and first touch.
Everything else: off by default. Notifications about lead status changes, sequence completions, and activity updates are useful when they're actionable. When they're background noise, reps tune out the whole notification channel, including the ones that matter.
Every notification that isn't directly tied to a next action is training your team to ignore all of them. Default to off and add back only what someone will act on.
The Whole Pass Takes One Afternoon
Rewriting statuses takes about 30 minutes, including testing them in a sample pipeline. Building the three smart views takes another 20. Setting up the starter sequence, with the email copy drafted properly rather than placeholder text, runs about 90 minutes if you're being honest about the writing. Custom fields are 15 minutes. Notification settings are 10. You're done in under four hours, usually less.
What you get on the other side is a CRM your reps can actually navigate. Status labels that match how they think about the pipeline. Views that surface what needs attention without manual searching. A sequence they can personalize rather than build from scratch. Fields that make pipeline reviews a conversation about deals instead of a conversation about what fields mean.
If you're inheriting a Close instance that's already a mess rather than setting up a fresh one, the approach is the same but slower. Fix the statuses first (data cleanup is impossible without consistent statuses). Then build the smart views, which start returning value immediately. Then audit the sequences and kill any that haven't been touched in 60 days. Work through it over a few weeks rather than trying to do it all at once.
The CRM that never got properly set up is the one everyone stops trusting. That trust, once lost, is very hard to rebuild.
If you're in the middle of a Close setup or a messy CRM cleanup and want to compare notes, reach out here. Happy to look at what you're working with.
Comments