22 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.
Sales Playground orgVersion 4.012 July 2026Google Calendar sync enabled
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 cannot tell who did what — unless you sign your work.
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.
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.
Dashboards → Sales Dashboard → Refresh. A two-week-old dashboard lies.
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.
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.