30 real situations from a salesperson's day — each with the exact clicks and the exact words to type. Written for our team, where everyone works in one shared Salesforce login — and where Rohan, your AI sales coach, reads it all.
Sales Playground orgVersion 7.0Updated 4 August 2026Rohan AI coach · LIVEDialer · Calendly · Email
R
Your AI Sales Head
Meet Rohan
Rohan is your AI sales coach. He reads the whole Salesforce board and posts in #sales-team three times a day — celebrating what you moved, flagging what slipped, and making sure no lead is ever dropped.
Tag him anytime. Type @Rohan in Slack and ask — “how am I doing today?”, “which of my deals are at risk?”, “what should I follow up first?” — he reads live Salesforce and answers right there in the thread.
New (Aug 2026): Rohan can now pull up call recordings and full transcripts, give you an AI read of any call (sentiment, talk-ratio, objections, coaching), and he flags anyone under-dialing or padding their task count. Ask “play Namrata’s last call” or “what did the customer object to?”.
The one catch
Rohan can only see your work if you follow the three golden rules below. He credits you by the name you sign on your tasks — an unsigned task belongs to nobody, so he can't put it on your scoreboard. Sign your work, log every call, book the next step: that is how Rohan makes you look good.
Updated — August 2026
What’s new since v1
Your calls log themselves. Every dialer call auto-saves to Salesforce with its recording. Stop creating “call” tasks by hand.
Only properly-signed tasks count. Write YOURNAME | Call/Demo – School – purpose. Blank “name call” placeholders are padding — Rohan now flags them instead of praising them.
Set the disposition on every call. Interested / Callback / Not Interested. No disposition = the call never reaches Salesforce and doesn’t count for you.
Rohan can do more. Recordings, transcripts, AI call analysis (sentiment, talk-ratio, objections, coaching), pipeline & at-risk deals — and he flags under-dialing and padding.
Initial Connect no longer errors. A deal moves stage even when the contact has no email (the auto-email just skips).
Call history is protected. Deleting a lead no longer deletes its calls. Still, don’t create a duplicate lead for a number that already exists.
Find your scenario
Something just happened? Find it below and jump straight to the steps.
We all work in one shared Salesforce account (“MLC Team”). Salesforce — and Rohan — cannot tell who did what unless you sign your work. These three rules are the whole game: follow them and Rohan coaches you accurately; break them and your effort goes uncredited.
Rule
What it means
1. Sign your work
Every task subject starts with your name in capitals and a | — “NAMRATA | Call – IMS Noida – demo follow-up”. Every comment starts with REP: your name. No signature means the work belongs to nobody — and Rohan cannot credit you for it.
2. Write it down
Every call, demo and proposal gets logged the moment it happens. If it is not in Salesforce, it did not happen.
3. Close the loop
Work finished → Mark Complete → create the next task. Never leave finished work showing as Open.
Subject formula
NAME | Action – School – Purpose. Actions: Call / Demo / Proposal / Follow-up / Payment. Example: “HARSH | Proposal – Arch College – ERP quote for 1200 students”.
Part 1
Every day
The daily rhythm: open your list, work it, log everything, close the day clean.
WhenEvery morning — before WhatsApp, before anything else.
Log in to Salesforce → click Tasks in the top bar.
Click the ▾ next to the list name → choose Open Tasks. (Our org's views: Open Tasks, Today's Tasks, Overdue Tasks, Recently Completed Tasks.)
Type your name in the Search this list... box — now you see only your tasks.
Red dates are late. Handle every red one first: done in real life → Scenario 5. Still pending → move its Due Date to today or tomorrow. Dead → comment why, then Mark Complete.
Read today's tasks top to bottom. That is your day plan.
The Tasks tab — list on the left, task detail and the Mark Complete button on the right.
Done whenZero red tasks under your name, and you know your first three calls of the day.
WhenThe moment you hang up. Sixty seconds — the most important habit in this playbook.
Open the task → pencil icon next to Comments → write four lines:
Type this
REP: Namrata
TALKED TO: Mr. Rajesh Sharma (Principal)
OUTCOME: Interested in fee module. Wants demo next week. Asked about WhatsApp integration.
NEXT STEP: Demo on Tuesday 15/07, 11 am, online.
Click Save, then Mark Complete.
Immediately create the next task (Scenario 4): “NAMRATA | Demo – Sunrise Public School – fee module, online”, due 15/07.
Did the deal move forward? Update the stage as well (Scenarios 9–12).
Done whenOld task Completed, comment saved, next signed task exists. Your stand-up numbers update themselves.
WhenNo answer, switched off, busy — you still log it, still sixty seconds.
Open the task → Comments:
Type this
REP: Namrata
TALKED TO: — (no answer, 2 attempts, 11:30 am and 4 pm)
OUTCOME: Phone not picked. WhatsApp sent asking for a good time.
NEXT STEP: Try again tomorrow morning.
Do not Mark Complete. Instead: pencil next to Due Date → change to tomorrow → Save.
NeverHang up and walk away, leaving the task to turn red. That is exactly how the org ended up with fifty overdue tasks nobody can explain.
Done whenThe task shows tomorrow's date and the attempt is on record.
WhenThe same day as the demo — before you go home, not tomorrow.
Open the demo event (or task) → write the outcome in its description or comment:
Type this
REP: Namrata
TALKED TO: Principal + accountant (40 min, online)
OUTCOME: Demo went well. They want a quote for 800 students incl. WhatsApp module.
NEXT STEP: Send proposal by tomorrow evening.
If it was a task: Mark Complete.
Opportunity path → Demo Completed → Mark Stage as Complete.
Create the task: “NAMRATA | Proposal – Sunrise Public School – quote 800 students”, due tomorrow.
A healthy deal (the real NIC opportunity) — stage path on top, every call logged in the activity timeline.
Done whenIn tomorrow's stand-up, “demos completed: 1” is already on screen. Nobody has to ask.
The deal stays in Quotation — don't touch the stage.
Keep one follow-up task alive. Each attempt: add a line to its comments (“3rd attempt 16/07 — no answer, WhatsApp sent”) and move the due date forward. The comment history becomes proof of your effort.
After 3–4 failed attempts: raise it in stand-up as a blocker — “waiting for customer response”. The manager decides: keep chasing or close it.
Done whenThe silence is visible in Salesforce — attempts logged, not hidden in your memory.
Open the three stand-up reports (Scenario 21) in three tabs.
Go person by person — each rep's name-block is visible in every report, because signed subjects sort alphabetically.
Closing rule: every rep's “next committed outcome” must exist as a signed task before the meeting ends. Not a task — not a commitment.
The Sales Dashboard — team totals. “Qualified Lead by Reps” always shows one MLC Team bar in our shared-login setup; per-person numbers come from the signed-subject reports.
Done whenEvery number discussed came off a screen.
Reports → New Report → search “Tasks” → choose Tasks and Events → Start Report.
Filters: Show Me = All Activities; Date = Completed Date – Yesterday; add Status equals Completed.
Columns: Subject, Related To, Comments. Sort by Subject — the name signatures group each rep's work automatically.
Save & Run → name it “Stand-up 1 — Completed Yesterday” → save in Public Reports.
Repeat twice with different filters:
Report
Filters
Answers
Stand-up 1 — Completed Yesterday
Status = Completed, Completed Date = Yesterday
“What did you complete yesterday?”
Stand-up 2 — Due Today
Status = Open, Due Date = Today
“What are you doing today?”
Stand-up 3 — Overdue (Blockers)
Status = Open, Due Date < Today
“Any blockers?”
To isolate one person, add the filter “Subject contains NAMRATA” — or simply use the search box on any task list view.
The Reports tab — the three stand-up reports join the existing sales reports here.
Done whenThree reports exist in Public Reports and open in one click every morning.
Part 5
Google Calendar
Salesforce is connected to the team's Google Calendar (Einstein Activity Capture, since July 2026). One rule: Events sync to Google Calendar — Tasks never do. Fixed date and time (demo, meeting) = Event. To-do work (calls to attempt, proposals to send) = Task. Changes sync both ways.
WhenA demo or meeting gets a fixed date and time. This replaces creating a demo task (see Scenario 9).
Open the school's opportunity (or lead) → Activity panel on the right.
Click the calendar icon (New Event) — next to the email, call and task icons.
Fill it in — signed, like everything else:
Type this
Subject: NAMRATA | Demo – Sunrise Public School – fee module
Start: 15/07/2026, 11:00 am
End: 15/07/2026, 11:45 am
Description: Principal + accountant attending. Google Meet link: [paste].
REP: Namrata
Save. Within a few minutes the event appears in the team's Google Calendar — visible on every rep's phone that subscribes to it.
Time changed? Move it in either place — Salesforce or Google Calendar — and the other side updates automatically.
After the demo, continue with Scenario 10 (stage → Demo Completed, outcome in the event's description).
Don'tCreate a Task for a demo and expect it on the calendar — Tasks never sync to Google Calendar. Fixed date + time = Event, always.
Done whenThe demo shows in Google Calendar with your name in the title — the whole team sees the day's demos without opening Salesforce.
Part 6 · Now live
Dialer
Calls made on the DialShree dialer now write themselves into Salesforce — automatically, with the disposition, duration and a playable recording. This removes the manual “log the call” step for dialer calls (only for dialer calls — your personal-mobile calls still need Scenario 5).
WhenYou make or take calls through the DialShree dialer (not your personal mobile).
Live since July 2026The dialer connection is switched on and proven. Every DialShree call now posts itself into Salesforce — you do nothing.
Do nothing. Every dialer call posts itself as a Completed Task on the matching Lead or Contact — subject “DialShree Call – <disposition>”, with the agent, campaign, number, duration and a link to the recording — a minute or two after you hang up.
It matches by phone number. If a call doesn't appear on a Lead, that Lead's Phone or Mobile is probably missing or wrong. Fix the number on the Lead so future calls attach. (Calls with no matching Lead still get logged, just unlinked — a manager reviews those.)
Don't double-log. If the dialer already logged the call, don't also type a manual call log for the same call — you'd end up with two Tasks. Just add a comment (Scenario 5 style) to the auto-created Task if you want to add detail or the outcome.
Personal-mobile calls still need Scenario 5. Only DialShree calls auto-log. Anything you dial from your own phone, you log by hand as usual.
A dialer call that logged itself — agent, campaign, number, disposition and duration in the Comments, with a Call Recording panel on the right.
Done whenDialer calls appear on the Lead's timeline on their own, and the only calls you log by hand are the ones from your personal mobile.
WhenYou want to hear what was actually said — before a follow-up, during a hand-over, or to settle a “what did they promise?” question.
Open the school's Lead or Contact → Activities panel → click the DialShree Call you want to hear (or open it from the Tasks list).
On the call's record, find the Call Recording panel (right side).
Press ▶ Play — the recording plays right there, in the page. No download, no separate app.
The Call Recording panel — press play and the call plays in the page.
If it doesn't playA recording only exists for calls that actually connected long enough to record. Very short / unanswered calls may have none — the panel will say so.
Done whenYou've heard the call and can act on what was really said — not on memory.
Part 7 · Now live
Meetings
Salesforce is connected to Calendly. Book a demo straight from a school's record with the details pre-filled — and every booking logs itself onto the record and pings #sales-team in Slack. No copy-pasting names or emails, no manual meeting log.
WhenA school agrees to a demo and you want to send them a booking link — with their name and email already filled in.
Open the school's Lead or Contact record.
Click the Book Calendly button in the top-right action bar (next to Edit / Delete).
Our Calendly booking page opens in a new tab with the school's name and email already pre-filled — just pick the demo type / slot, or share the link with them.
The Book Calendly button on a Lead — one click opens Calendly with the school's name and email pre-filled.
Why it mattersThe invitee details come straight from Salesforce, so the booking always matches the right school — which is what makes Scenario 26 (auto-logging) work.
Done whenThe school has a booking link (or a booked slot) with their details already in it — no retyping.
WhenAnyone books, reschedules or cancels a meeting through Calendly.
Do nothing in Salesforce. The meeting posts itself as an activity on the matching Lead/Contact (matched by the invitee's email) — “Calendly Meeting – <name>”, with the time. A cancellation updates it too.
At the same moment, a message drops into #sales-team in Slack (📅 new booking / ❌ cancelled) with the invitee, the time and the host.
Still move the deal. Auto-logging records the meeting; it does not move your pipeline. When the demo is fixed, set the opportunity stage to Demo Scheduled (Scenario 9); after it happens, Demo Completed (Scenario 10).
A Calendly booking that logged itself onto the school's record — matched automatically by the invitee's email.
Match by emailThe booking attaches only if the invitee's email matches a Lead or Contact in Salesforce. If a booking doesn't appear on a record, the email on that Lead/Contact is missing or different — fix it so future bookings attach.
Done whenThe meeting is on the school's timeline and in #sales-team without anyone logging it — and the opportunity stage reflects it.
Part 8 · Now live
Email
Emails you exchange with a school now attach to its Salesforce record automatically, so the whole conversation lives on the timeline — not just in your inbox. Received emails log on their own; to also capture what you send, add one BCC line to your mailbox once.
WhenYou email a school from your @myleadingcampus.com mailbox, or a school emails you.
Received email — automatic. When a school emails your work mailbox, it logs itself as an activity on the matching Lead/Contact (matched by the sender's email). You do nothing.
Sent email — one-time setup, then automatic. To capture what you send, add this BCC to your mailbox once (Hostinger webmail → ⚙ Settings → Account → Bcc field → paste → Save):
BCC address — paste once into your mailbox settings
After that, every email you send to a school is silently copied to Salesforce and lands on that school's record — matched by the recipient's email.
An email on the school's timeline — the conversation lives on the record, not just in an inbox.
Two things to know1) It attaches only when the school's email matches a Lead/Contact — keep email addresses on records correct. 2) Salesforce also sends on behalf of @myleadingcampus.com (verified domain), so emails from Salesforce look like they came from us, not a stranger.
Done whenYour email trail with each school sits on its Salesforce record — visible to whoever picks the school up next.
Part 9 · Cold calling
Cold calling
Cold calls run through the DialShree dialer and log themselves (Part 6). But two things are on you — and both decide whether your effort ever counts: picking the right disposition, and working the interested ones. Get these wrong and a real prospect — even a closed sale — vanishes.
28Pick the right disposition — it decides everythingIndex ↑
WhenEvery cold call, the moment you hang up — you choose an outcome in the dialer.
Your disposition is not admin — it is the switch that decides whether a lead is created and whether you get credit. Tell the truth about what happened:
You tap…
What it means
What happens
Interested
They want to know more.
✅ Lead created
Call Back / Callback
“Call me later.”
✅ Lead created
Follow UP
Real conversation, more to do.
✅ Lead created
Sale Made
They said yes.
✅ Lead → then Scenario 30
Connected
Vague “I talked to someone.”
❌ No lead — the trap
Not Interested
A clear no.
Logged, no lead — respect it
Busy / No Answer
Didn't reach a person.
Logged, no lead
Don'tDump everything into “Connected.” It creates no lead and tells us nothing. If the person was keen, tap Interested or Call Back — otherwise that hot lead is never created and your good call counts for nothing.
Done whenEvery call carries its true outcome — so the interested ones become leads and the dead ones stay out of the pipeline.
29You got an interested cold call — make it a real leadIndex ↑
WhenA cold call went well and you tapped Interested / Call Back. The system just made a placeholder lead named “Cold Call 98…” — flesh it out while it's fresh.
WhyA lead called “Cold Call 9405812160” with no name and no next step is not workable — it sits and goes cold. Two minutes now turns it into a real prospect.
Open Leads → find your new “Cold Call <number>” (Status New, at the top). Or open it straight from your call in the Activities list.
Edit and fill in what you learned: Last Name (the person / school — replace “Cold Call 98…”), Company (the school), Email, and their need in the Description.
Sign it & book the next step — create a Task: NAME | Follow-up – School – what you agreed, dated for when you promised to call back (Scenario 5 style).
Save. It's now a named, owned, workable lead with a next step — not a stray phone number.
Rohan is watchingLeave an interested lead with no next step booked and Rohan flags it in #sales-team with your name on it. Book the follow-up before you move to the next call.
Done whenThe placeholder has a real name, a school, and a signed next-step task — and Rohan counts it as your live prospect.
30You closed a sale on a cold call — make it countIndex ↑
WhenA cold call ended in a yes and you tapped Sale Made. That tap is not the sale — the sale only exists once it's an Opportunity marked Closed Won.
The trap“Sale Made” is only a note on a call. On its own it puts zero in the pipeline and the numbers. A sale nobody recorded is a sale that didn't happen — no credit, no revenue on the board.
Open the Lead (the “Cold Call 98…” one, or the existing school lead the call attached to).
Fill in the real details first (Scenario 29) so the record is clean.
Click Convert — turn the Lead into an Account + Contact + Opportunity (Scenario 8 walks the convert screen).
On the new Opportunity: set the Amount, move the Stage to School Onboarded / Closed Won, and create the payment task (Scenario 12).
Why it mattersRohan's forecast and the company's revenue numbers count Opportunities, never call notes. A “Sale Made” that never became a Closed Won Opportunity is invisible to both. Convert it — or it didn't happen.
Done whenThe sale is a Closed Won Opportunity with an Amount — it shows in the pipeline, the revenue numbers, and against your name.
Reference
Cheat sheet
The two templates the whole system runs on. Copy, replace the brackets, done.
Task subject (replace NAME with your name in capitals)
Copy-paste
NAME | Call – [School] – [purpose]
NAME | Demo – [School] – [module], [online/at school]
NAME | Proposal – [School] – [what you are quoting]
NAME | Follow-up – [School] – [what you are chasing]
NAME | Payment – [School] – [what to collect]
After-call comment
Copy-paste
REP: [your name]
TALKED TO: [name + role]
OUTCOME: [what they said, 1–2 lines]
NEXT STEP: [what happens next + when]
Remember
If it is not in Salesforce, it did not happen. And in a shared account, work without your name on it is work nobody can credit you for.