9:14
●●●● 5G ▮▮▮
Tuesday
19 May · 5 interviews today
S
Today
11:00
13:00
14:00
16:00
17:30
Tanvi (StagBuzz) · channel preference
9:32 AM · prefers email over WhatsApp
Tanvi said · WhatsApp
"Hey Suchal, can we move candidate communications to email going forward? WhatsApp is getting cluttered for me. Same for the slot proposals."
Affects 2 active StagBuzz rounds. Channel switch is a global setting per client. Tanvi-only or all-clients? Pick below.
Decision needed
Apply the channel switch?
Recommended · StagBuzz only
Switch StagBuzz candidate comms to email. Other clients stay on WhatsApp.
Draft · reply to Tanvi
"got it Tanvi — switching to email for StagBuzz candidates from today. will send next batch via email. let me know if you want to revert anytime."
System change
StagBuzz client setting: candidate channel WhatsApp → Email. Affects 2 active rounds (Marketing Lead, Performance Marketer). Slot proposals also flip to email.
Apply to all clients
Global switch: candidate comms move to email across every client. Bigger change — only do this if you're standardizing.
Draft · reply to Tanvi
"got it Tanvi — switching to email for all candidate comms from today. let me know if you want to revert anytime."
System change
Global candidate channel WhatsApp → Email. Affects 11 active rounds across 5 clients. No client other than Tanvi has asked for this yet.
Recommend StagBuzz-only unless you've heard the same from other HMs.
Push back · keep WhatsApp default
Suggest hybrid: WhatsApp stays default, but Tanvi gets bcc'd via email so she can scan in one inbox.
Draft · reply to Tanvi
"hey Tanvi — totally get the inbox clutter. one option: I keep candidate comms on WhatsApp (faster response rate) but bcc you on email so you can scan in one place. want to try that for a week?"
No system change applied until Tanvi confirms.
Aakshay (Qpi) · can't make tomorrow
9:48 AM · 4 interviews to reshuffle
Aakshay said · WhatsApp
"Hi Suchal, dental thing came up tomorrow. Can we push all my Tech Recruiter interviews to Thursday? Same times if possible."
I don't have Aakshay's Thursday calendar. He said "same times if possible" which is a hint, but candidates need their own confirmation too. Cleanest flow: confirm Thursday window with Aakshay first, then ask each candidate. Below are the options.
Decision needed
Reschedule 4 candidates · pick the approach
Recommended · confirm Aakshay first, then ask each candidate
Ask Aakshay if Thursday same-times specifically works (vs general "Thursday"). Once locked, draft individual messages to each of the 4 candidates.
Draft · reply to Aakshay
"no worries Aakshay — confirming Thursday so I can line up the candidates. 11 AM (Aman), 2 PM (Priya), 5 PM (Aakash), 6 PM (Sneha) — all 4 fine? happy to shift any if needed."
Candidate messages drafted but held until Aakshay confirms the 4 slots.
Send all 5 now (assume Aakshay's "same times" is firm)
Trust Aakshay's hint; send the 4 candidate drafts in parallel + a reply confirming. Faster, slight risk Aakshay later flags a new conflict.
Draft · reply to Aakshay
"no worries Aakshay, moving all 4 to Thursday same times. will confirm with candidates and update you by 11 AM."
Draft · to Aman (11 AM slot)
"hey Aman — quick reschedule, Aakshay can't make Wed. shifting your Tech Recruiter interview to Thu 11 AM same time. works for you? let me know."
Draft · to Priya (2 PM slot)
"hey Priya — Aakshay had a conflict Wed. shifting your interview to Thu 2 PM same time. ok with that? lmk."
Draft · to Aakash (5 PM slot)
"hey Aakash — Aakshay can't make Wed. moving your slot to Thu 5 PM, same time. works?"
Draft · to Sneha (6 PM slot)
"hey Sneha — Aakshay had to push Wed. moving your slot to Thu 6 PM same time. all good? lmk."
Review each individually
Open the 4 candidate threads one at a time. Useful if you want to tweak tone per candidate or if any is fragile.
What happens
Each candidate becomes its own task in Inbox. You confirm/edit the draft per candidate; the Aakshay reply goes only after all 4 are sent.
Tuesday
19 May · 5 interviews today · Inbox: 14
S
Today
11:00
13:00
14:00
16:00
17:30
Schedule 3 for Tech Recruiter
Qpi · Jenny · just now
Jenny said · WhatsApp
"Need 3 tech recruiter candidates, slots Wed 5/6/7 PM. ASAP — we're moving fast on this role."
Wed 5 PM
Wed 6 PM
Wed 7 PM
Drafted messages · 3
1
Priya M
91% fit
5y tech-recruiter at Razorpay. Replied "interested" Sun. Never ghosted.
WhatsApp draft
hey Priya! quick one — Qpi tech recruiter role wants to interview tomorrow. they have 5, 6, or 7 PM open. any work? 30 min.
2
Aakash R
88% fit
New to your pipeline. 7y experience, ex-Freshworks.
WhatsApp draft
hi Aakash, Suchal from Scouto. saw you on the tech recruiter shortlist for Qpi — they're moving fast, want to interview tomorrow. 5, 6, or 7 PM. any work for a 30 min chat?
3
Sneha T
85% fit
Said "next week ok" 3 days ago. Worth nudging.
WhatsApp draft
Sneha hey! qpi tech recruiter is moving fast — they want tomorrow. 5/6/7 PM. you said next week is ok so totally up to you, but if tomorrow works i can squeeze you in.
Schedule 3 for Tech Recruiter
Qpi · Jenny · 15 min ago
Replies · 2 of 3
Auto-pilot doing the simple, escalating the edges. Priya's clean yes — handled. Aakash's counter — within Jenny's slot window so auto-accepted. Sneha — will surface as an inbox item at 2:42 PM if she hasn't replied.
Synced to PyjamaHR: Priya → AI Interview · 6 PM Wed. Aakash → AI Interview · 7 PM Wed. Sneha → status unchanged. Updates pushed at 10:58, 10:59.
Aman R · Tech Recruiter
Qpi · Jenny + Aakshay · 11:00 (in 5 min)
All ready
starts 11:00
Aman (candidate)
opened invite · not joined yet
Jenny (Qpi)
opened invite · not joined yet
Aakshay (Qpi)
opened invite · not joined yet
Meet link · open access
meet.google.com/abc-defg-hij
No friction expected. I'll watch this and only ping you if someone hasn't joined by 11:03 or if there's a wrong-email issue.
Aman R · Tech Recruiter
Live · 1 min in · alert
Live · candidate in waiting room
T+1 alert
Aman
joined with wrong email · waiting room
Jenny
joined 11:00 · waiting for Aman
Aakshay
joined 11:01
Wrong-email rescue
Aman just texted: "Suchal I'm in the wait room — used my work email by mistake. Can someone let me in?"
I just did this
Auto-admitted Aman from waiting room (Meet API). He's in the call now. Jenny didn't notice; Aakshay didn't notice. Crisis avoided · no manual rescue needed.
Note: We use accessType: OPEN on Meet — there shouldn't be a waiting room. Aman joined from outside the invite scope (work email vs personal). My fallback caught it via the Meet host API.
This is the wedge. The exact moment Suchal flagged in her May 12 examples ("candidate had actually joined from a different email ID and was stuck in the waiting room until I had to join the meeting and let him in"). Cockpit handled in 14 seconds. Zero Suchal involvement.
Aman R · Tech Recruiter
Live · 3 min in
Live · Aakshay not joined
T+3
Aman
joined 11:01
Jenny
joined 11:00
Aakshay
not joined
Drafted message for Aakshay
"hey akshay, aman's interview is in progress, jenny's on the call. just a heads up :)"
Max 1 nudge per side per interview. Quiet, not chatty. If Aakshay's still missing at T+5, I'll escalate to you (notif).
Krithika paused Backend Engineer
Cupa · 13:15
Krithika said · WhatsApp
"Suchal, can we pause Backend Engineer for 2 weeks? We want to focus interviewer bandwidth on the Designer role this sprint. Will let you know when to resume."
I caught this and queued 3 actions:
1. Update PyjamaHR: Backend Engineer → status on_hold (2-week pause noted)
2. The 4 candidates already in pipeline get a status note (no message sent — they're not expecting one)
3. Stop the daily "send 2 more candidates" auto-batch for Backend Engineer
Awaiting your confirmation before I push to PyjamaHR.
1. Update PyjamaHR: Backend Engineer → status on_hold (2-week pause noted)
2. The 4 candidates already in pipeline get a status note (no message sent — they're not expecting one)
3. Stop the daily "send 2 more candidates" auto-batch for Backend Engineer
Awaiting your confirmation before I push to PyjamaHR.
Reply to Krithika
"got it Krithika. pausing Backend Engineer for 2 weeks. Designer is now the focus — I'll pipe more candidates there. Ping me when you want to resume Backend."
Maria S · Applied AI
Escalation · 2 hours before interview
Decision needed
Maria just messaged: family emergency, can't make 4 PM today.
Maria: "family emergency, can't make 4 PM, can we reschedule?" (sent 1:53 PM via WhatsApp)
Jenny's stance last week: "reject if she can't reschedule on the day." You overruled then and saved Maria. Pattern: you've overruled-reject 3 of 5 times in similar moments.
Recommended · push Jenny on Wed 6 PM
Pitch the Wed 6 PM swap; hold Maria's reply until Jenny confirms.
Draft · to Jenny
"hey Jenny — Maria just hit a family emergency, can't make 4 PM. you'd mentioned Wed 6 PM also works for you (your WhatsApp last Tue). want to swap to that? phone format fine if you're moving around."
Draft · to Maria (held until Jenny replies)
"totally understand, hope everything's ok at home. checking with Jenny on Wed 6 PM — will confirm within 30 min."
Just reschedule
Ask Maria for her windows first; loop Jenny once she replies.
Draft · to Maria
"totally understand, hope everything's ok. quick q — what windows work for you over the next few days? once you share, I'll line it up with Jenny."
Two-step: Maria's reply → ask Jenny → confirm with Maria. I don't have Jenny's calendar, so can't pre-propose her slots.
Push Jenny on her earlier stance
Surface family-emergency context to Jenny. She decides reject or one more shot.
Draft · to Jenny
"Maria just bailed on 4 PM — family emergency. last week you said reject if she can't reschedule on the day. family emergency feels different from no-call no-show. want to hold that line, or give her one more shot? your call."
Maria-side reply drafted after Jenny responds. No candidate action until client HR confirms.
Let me handle this
Dismiss the card. You'll message both directly.
Devendra (EatCookJoy) urgent ping
14:38 · founder-CEO · same-day urgency
Devendra said · WhatsApp
"URGENT — need an Ops Lead before Monday. We just lost our current Ops person, expanding 3 cities next week. Anyone you can pull from the pipeline? Will pay urgency premium."
Founder pings get fast-tracked. Devendra is EatCookJoy's CEO. I've ranked candidates by ops experience + can-start-this-week + relevant city background. Top 3 below.
Top 3 · Ops Lead
1
Tarun S
93% fit
8y ops at Zomato + Swiggy. Just left Swiggy, available immediately. Bangalore + Pune background.
WhatsApp draft (Devendra urgent tone)
hey Tarun! quick one — EatCookJoy (food tech, 3-city expansion next week) urgently needs an Ops Lead. start Monday. would you be open to chatting today? CEO wants to fast-track.
2
Anjali K
87% fit
6y ops at Dunzo + BlinkIt. Open to new role. Mumbai-based.
WhatsApp draft
Anjali! EatCookJoy urgently needs an Ops Lead, joining Monday, 3-city rollout. interested in a fast-track chat today?
3
Vijay R
82% fit
5y ops + 2y consulting. Wants more execution. Chennai-based.
WhatsApp draft
Vijay, EatCookJoy founder urgently needs an Ops Lead Monday. multi-city rollout coming. drop me a line if you can do a call today?
How to send
Pick the outreach scope, then confirm.
Recommended · send all 3 + reply Devendra
Three parallel candidate threads + a quick ack to Devendra so he knows you're on it.
Draft · reply to Devendra
"on it. 3 strong Ops Lead candidates with relevant city + food tech background — Tarun (Swiggy/Zomato, immediate), Anjali (Dunzo/BlinkIt), Vijay (5y ops). messages going out to them now. will keep you posted on responses today."
Send only Tarun (top fit)
Highest-confidence candidate first; reach Anjali/Vijay only if Tarun is unavailable.
Draft · reply to Devendra
"on it. Tarun's the strongest fit — 8y at Zomato + Swiggy, can start Monday. message going out to him now. holding Anjali/Vijay as backups. will update by EOD."
Ask Devendra to narrow the spec first
3 cities is a lot. Get clarity on which city is highest priority before blasting all 3.
Draft · reply to Devendra
"got it. quick q before I message — which city goes live first? Tarun is Bangalore/Pune, Anjali Mumbai, Vijay Chennai. Want to lead with the one closest to your priority city?"
No candidate messages sent until Devendra answers.
Pipeline drift detected
Cupa · daily 3 PM scan · 15:22
Status drift
Yusuf K hasn't moved in 47 days. I pinged Krithika, she just replied.
Krithika: "Oh — Yusuf joined us on April 15. Sorry, we should've told you, totally slipped through. Can you mark him hired? Anyone else still active?"
I ran a daily drift scan at 3 PM. Yusuf has been in "move ahead" since April 30, no client update. Asked Krithika 22 min ago. She confirmed: hired without telling us.
Update Yusuf → hired (April 15)
PyjamaHR write only. No client message, no invoicing. Reversible.
PyjamaHR update
Yusuf K · status: "Move ahead" → "Hired" · hired date: April 15, 2026 · source: Krithika confirmed via WhatsApp 22 min ago.
Mark fee invoice eligible (Cupa)
Flag this placement for billing. Doesn't send the invoice yet, just flags it for the monthly run.
Billing flag
Placement: Yusuf K @ Cupa · hire date April 15 · fee tier: Engineering (standard). Flagged for May invoice batch. No email sent to Cupa yet.
Requires Yusuf marked hired first.
Ping the 3 other Cupa candidates
Confirm their status. If they're still active for other roles, keep them in pipeline; if dropped, archive.
Draft · to Krithika (Cupa)
"thanks for the heads up on Yusuf, will update. quick one — Priya, Rohan, and Manish are also in pipeline for other Cupa roles. any of them already hired or on hold? want to make sure we're not duplicating effort."
Sweep remaining roles for untold-us hires
Trigger drift scan on all other active clients (StagBuzz, EatCookJoy, PaisaWise, Qpi). Read-only — surfaces candidates that look hired but haven't been confirmed.
Drift scan scope
4 clients · 11 active roles · ~80 in-pipeline candidates. Flags candidates in "Move ahead" status for > 30 days with no recent client message. Results appear in your Inbox as drift items.
No outbound messages from this scan. You review each surfaced item separately.
Calendar conflict at 4 PM
Cross-client · 2 interviews · same time
Conflict
Two interviews want 4 PM tomorrow. Both want you on the call.
Qpi · Applied AI: Jenny just asked you to slot Tara at 4 PM tomorrow.
StagBuzz · Marketing: You already confirmed Saurabh's panel interview at 4 PM tomorrow.
StagBuzz · Marketing: You already confirmed Saurabh's panel interview at 4 PM tomorrow.
Both interviews need you present (Qpi wants you for warm-up, StagBuzz needs introductions). They can't both happen at 4 PM with you in the room.
Recommended · push Qpi to 5 PM
Ask Jenny to slide by 1 hr so you can still cover StagBuzz at 4 PM.
Draft · to Jenny
"hey Jenny — got a clash with another client at 4 PM tomorrow (already locked). you'd said you were flexible last Mon — can we push Tara's interview to 5 PM same day? I'll be on the call for warm-up."
Draft · to Tara (held until Jenny confirms)
"Tara — slight tweak, looking at 5 PM tomorrow instead of 4 PM. will confirm shortly."
Skip your warm-up for Qpi
Send Tara direct to Jenny; you skip the warm-up, check in post-call.
Draft · to Jenny
"Jenny, got a clash with another client at 4 PM. Tara is briefed — she can join directly with you, I'll check in post-call. ok?"
Draft · to Tara
"Tara, slight change — I won't join the warm-up tomorrow, head straight to the Jenny call at 4 PM. quick brief: keep it conversational, she likes specifics on past wins. I'll check in after."
Ask StagBuzz/Tanvi to move instead
Push StagBuzz; Tanvi was flexible last time. Ask first, no candidate draft yet.
Draft · to Tanvi
"Tanvi quick one — got a clash at 4 PM tomorrow for Saurabh's panel. any chance we slide it by an hour, or same time Thursday? you'd said you had flex last time."
No candidate-side draft yet — depends on what Tanvi confirms. I don't have her calendar so it's ask-first.
Aman R · Tech Recruiter
Ended 11:32 · 31 min
Capture outcome?
To Jenny (Qpi)
"hey, how did aman go? want me to schedule the next round with akshay + the panel?"
To Aman (candidate)
"hey aman, how did the interview go? any thoughts? happy to share feedback when jenny sends it across."
When replies come in, I'll surface them in your Inbox under Outcomes and ask before updating PyjamaHR.
Tuesday
19 May · 5 of 5 done
S
Today · all done
11:00
13:00
14:00
16:00
17:30
Day recap. 5 interviews. 4 outcomes captured live. Maria rescued. Aakshay rescheduled 4 to Thursday. Yusuf billed to Cupa. Devendra has 3 candidates messaged. Tanvi's preference updated. Have a good evening, Suchal.
Inbox
14 open · 3 needing decision
S
Needs decision3
Maria S · Qpi Applied AI
1:53 PM
Family emergency. Jenny said reject; you overruled last time. 3 options ready.
Vikram K · Qpi Tech Recruiter
held 4d
Jenny shared feedback but no verdict ("not hungry enough"). 4 ways to push her drafted.
Mohammed I · PaisaWise Risk Engineer
17 min
"Daughter is sick — can we push interview to Thursday?" Drafted holding reply + ask to Akshat for Thu slots.
Time-sensitive3
Tech Recruiter Wed batch · 1 of 3 sent
10:42 AM
Jenny asked at 10:42. Priya sent + replied. Aakash + Sneha drafts ready, not sent.
Aakshay rescheduled tomorrow
9:48 AM
4 candidates need reschedule to Thursday. 4 drafts ready, awaiting batch send.
Maria interview 16:00 · decision pending
2h ahead
Linked to the decision above. Decide before 3 PM.
Follow-ups5
Sneha T · no reply
4h
Tech Recruiter Wed slots. Nudge drafted.
Krithika (Cupa) · no reply
2d
Optimization Scientist status check. Re-ping drafted.
Aakash R · slot proposal
3d
Tech Recruiter. Check-in drafted.
Priya M · "let me check"
2h
Wait or nudge? Wait recommended.
Pratiksha (PaisaWise) · no reply
1d
Compliance role status. Asked if still active.
Outcomes pending3
Rohan K · interview ended 17:55
2h ago
StagBuzz Marketing. Feedback messages drafted.
Sneha T · rejected
ready
Rejection feedback drafted. Send when you confirm.
Aman R · moved to next round
ready
Schedule round 2 with Akshay + panel? Drafted slot proposal ready.
Captured · need confirmation3
Tanvi preference change → email
9:32 AM
Confirmed StagBuzz comms → email. 2 templates updated.
Krithika paused Backend (2 weeks)
13:15
PyjamaHR updated. Backend candidates pipelined to Designer review.
Yusuf hired April 15 (Cupa)
15:22
Krithika confirmed. PyjamaHR updated. Invoice queued.
Inbox · Decisions
3 awaiting you
S
Filtered to Needs decision. These are the moments where the agent prepped context but won't act without your tap.
Maria S · family emergency
1:53 PM
Reschedule, reject as Jenny prefers, or phone-format pitch. 4 options drafted.
→ decide
Vikram K · Jenny hasn't decided
held 4d
Jenny shared concerns ("not hungry enough") but no verdict. 4 ways to push her drafted.
→ how to push
Mohammed I · reschedule request
17 min
Daughter is sick. Need to ask Akshat for Thu slots. Reschedule (2-step) or offer phone format today.
→ decide
Clients
5 active · 25 open roles · 4 actions pending
S
Active
Q
Qpi
5 roles · Jenny, Aakshay, Neha
3 actions
C
Cupa
8 roles · Krithika, Riya · 1 paused
1 action
S
StagBuzz
5 roles · Tanvi, Saurabh · email-preferred
clear
E
EatCookJoy
3 roles · Devendra (CEO) · urgent pings
1 urgent
P
PaisaWise
4 roles · Akshat, Pratiksha · new client
new
Qpi
5 roles · 1 paused · Jenny, Aakshay, Neha (new)
Relationship signal
Jenny last talked: Mon AM. Aakshay: Today 9:48 (dental decline). Neha: added Wed — taking over Applied AI from Jenny.
Open roles
Tech Recruiter
3 actions
Jenny + Aakshay panelists · Jenny's the lead
12 Applied · 3 AI Interview · 2 Move Ahead · 8 Rejected
Applied AI
1 stalled
Neha taking over from Jenny · 5 candidates haven't moved in 14d
9 Applied · 5 Move Ahead · 3 Rejected
Optimization Scientist
clear
2 interviews scheduled this week
7 Applied · 2 AI Interview · 1 Move Ahead
iOS Engineer
clear
slow burn · 1 interview/wk
14 Applied · 1 AI Interview · 1 Move Ahead
Senior PM
paused
Paused last Mon · captured from call with Jenny
PaisaWise
4 roles · new client · Akshat, Pratiksha
Relationship signal
Akshat (Eng Manager) last talked: Yesterday PM · kickoff call. Pratiksha (HR): no recent interaction. Next 1:1 with Akshat: Friday 11 AM.
New client onboarded last week. Fintech, ~120 person company. Akshat owns engineering hires, Pratiksha owns compliance roles. Tone-learning corpus thin — first 5 outreach messages will surface to you for review before sending.
Open roles
Risk Engineer
active
Akshat panelist · today's 1 PM interview with Mohammed
8 Applied · 3 AI Interview · 1 Move Ahead
Senior Backend
active
Akshat panelist · 4 interviews this week
11 Applied · 4 AI Interview · 2 Move Ahead
Compliance Officer
1 action
Pratiksha panelist · just hired externally?
6 Applied · 0 in active stages
Senior Product Designer
slow
Akshat panelist · 2 interviews scheduled
15 Applied · 2 AI Interview · 0 Move Ahead
Tech Recruiter
Jenny + Aakshay · open · ↗ PyjamaHR
Needs your action3
Schedule Aman + Priya + Sneha for Wed
10:42
Jenny asked. Slots Wed 5/6/7 PM. 3 drafted messages ready.
Follow up with Sneha
4h, no reply
Wed slot proposal. Drafted nudge ready.
Vikram K · push Jenny for verdict
held 4d
4 ways to push Jenny drafted.
Priya M
#PHR-1077
scheduling
+ schedule · WhatsApp · move
Aakash R
#PHR-1102
confirmed
+ panel invite · WhatsApp · move
Sneha T
#PHR-1052
no reply
+ nudge drafted · skip · WhatsApp
Applied AI
Neha taking over from Jenny · 1 stalled
Drift detected5
5 candidates haven't moved in 14d
daily scan
Maria, Yusuf, Reena, Manav, Aarav — all in "Move Ahead" stage. Drafted "any update?" to Neha.
Neha just took over from Jenny
Wed
Drafted intro context for Neha: 9 candidates in pipeline, 5 stale, you can re-pipe.
Maria S
#PHR-2103
decision needed
→ inbox
Yusuf K
#PHR-1908
hired · billable
Reena B
#PHR-2055
stale
+ ping drafted
Day-2 · HM call captured
Jenny call · 10:30 AM · 3 min · auto-transcribed
Future feature (Week 3+). Scouto app on Suchal's dedicated work phone listened to her HM call (with consent), transcribed it, extracted 4 distinct updates. Each one needs its own confirmation before any system write.
4 updates extracted
Confirm each update separately. Each = one write.
Update 1 · Senior PM + DevOps Lead → paused
Jenny confirmed these 2 roles are on hold. PyjamaHR status flip + active-candidate notice.
PyjamaHR update
Senior PM (Qpi) · status: Active → Paused. DevOps Lead (Qpi) · status: Active → Paused. Source: Jenny call 10:30 AM (auto-transcript).
Draft · candidates currently in pipeline
3 active candidates on Senior PM, 2 on DevOps Lead. Drafted holding note: "hey [name], quick update — Qpi paused this role for now. I'll reach out the moment it reopens. happy to also share other roles in flight if you want."
Update 2 · Add Aakshay to Tech Recruiter panel
Default panel composition change. Future interviews include Aakshay.
PyjamaHR update
Role: Tech Recruiter (Qpi) · default panel: [Jenny] → [Jenny, Aakshay]. Applies to all future interview scheduling for this role. Existing scheduled interviews unchanged.
Draft · heads-up to Aakshay
"hey Aakshay — Jenny just added you as default panelist on Tech Recruiter role. you'll start seeing scheduling pings from me. flag if any timing concerns."
Update 3 · Maria flagged for reconsideration
Profile note only. No candidate-side action until Jenny formally re-opens.
PyjamaHR note
Maria S (Applied AI) · profile note added: "Jenny open to reconsidering — discussed on 10:30 AM call." Flag for next pipeline review batch.
No message to Maria yet. She doesn't know she's being reconsidered.
Update 4 · Add Neha as new Qpi HM
Neha takes over Applied AI from Jenny on Wednesday. New HM contact + role transition.
PyjamaHR update
Add Neha M as Qpi HM contact. Role: Applied AI · transfer ownership Jenny → Neha effective Wednesday. Keep Jenny on Tech Recruiter.
Draft · intro to Neha (queued for Wed)
"hi Neha, welcome to Qpi! Suchal here from Scouto — we run your active recruiting. I'll send you context on Applied AI pipeline (9 candidates, 5 stale) and the Jenny handover doc tomorrow morning. happy to jump on a quick 15-min onboarding call this week if helpful."
Held until Wed morning so it doesn't pre-empt Jenny's own intro.
Vikram K · Jenny hasn't decided
Qpi Tech Recruiter · held 4d · push Jenny for the call
Jenny's feedback (Wed interview) · no verdict yet
"Strong technical, good communicator. But I'm not sure he's hungry enough — last 2 years at MNC, came in late, left exactly at 6. Not a culture fit but skills check out."
Push Jenny — she decides
How do you want to push Jenny? Her call, not yours.
Jenny's borderline. Pattern (from your past Jenny threads): "not hungry enough" came up 3 times before. You pushed back on 2; one became an offer. Useful context for how to frame the push.
Recommended · push + share your read
Acknowledge the concern is real but coachable; offer round 2 or close. Easy reply for Jenny.
Draft · to Jenny
"on Vikram — skills check out cleanly. The hungry-enough concern is real but coachable IMO. round 2 with Akshay to dig deeper, or close it out? happy either way."
Push harder · advocate for advancing
Stronger advocacy. Useful when you genuinely think Jenny is missing the right call.
Draft · to Jenny
"Vikram's skills are exactly what you wanted. Worth Akshay's call before we close. I can set up round 2 today if you say go."
Agree with Jenny · close it out
Confirm Jenny's read. Rejection draft to Vikram held until she explicitly closes.
Draft · to Jenny
"agreed, not the fit. closing him out — will send a thoughtful no to Vikram unless you want to handle it."
Draft · to Vikram (held until Jenny confirms close)
"hey Vikram — thanks for taking the time with Qpi. they decided not to move forward on this round. specific note: they were looking for a tighter culture fit alongside the strong technical. happy to keep you on file for the next role that fits better. appreciate you."
Just remind, no opinion
Neutral nudge. Useful when you genuinely have no read or want Jenny to decide unprompted.
Draft · to Jenny
"Jenny what's the call on Vikram? round 2 or reject? happy either way, just need the nod."
What happens after Jenny replies: her "round 2" or "reject" triggers the next action — schedule round 2 OR send rejection feedback to Vikram. Until then, no candidate-side action.
Mohammed I · reschedule request
PaisaWise Risk Engineer · 13:00 today
Mohammed said · WhatsApp · 17 min ago
"Suchal sorry to do this last min — my daughter is sick, can't make 1 PM. Can we push by a day or do it Thursday?"
I don't have Akshat's Thursday availability yet. Drafted (1) a holding reply to Mohammed so he's not waiting and (2) a question to Akshat asking what slots work. Once Akshat replies, I'll come back to you with proposed times.
Drafted · holding reply to Mohammed
"hope your daughter gets better soon. let me check with Akshat on Thursday slots, will come back to you within the hour."
Drafted · question to Akshat
"hey Akshat, Mohammed (Risk Engineer round 2) needs to push tomorrow's 1 PM — his daughter is sick. what Thursday slots work for you? happy to slot it whenever works."
Mohammed I · waiting on Akshat
PaisaWise Risk Engineer · holding reply sent
Status: Holding reply sent to Mohammed at 12:43. Question to Akshat sent at 12:43. Waiting on Akshat's reply. Will surface as a new Needs You card the moment he replies with slots.
Sent · to Mohammed · 12:43
"hope your daughter gets better soon. let me check with Akshat on Thursday slots, will come back to you within the hour."
Sent · to Akshat · 12:43
"hey Akshat, Mohammed (Risk Engineer round 2) needs to push tomorrow's 1 PM — his daughter is sick. what Thursday slots work for you?"
Mohammed I · Akshat replied
PaisaWise Risk Engineer · 28 min after asking
Akshat said · WhatsApp · 13:11
"Thu 2 PM or 4 PM works for me. Pick whichever Mohammed prefers."
Thu 2 PM
Thu 4 PM
Akshat's quoted slots (from his WhatsApp above) → 2 PM and 4 PM Thu. Drafted follow-up to Mohammed with these exact slots.
Drafted · follow-up to Mohammed
"hey Mohammed, Akshat said Thu 2 PM or 4 PM works. either of those? once you pick i'll send the Meet invite."
Sneha T · 4h no reply
Qpi Tech Recruiter · Wed slots pending
Sneha got your message at 10:43 AM about Wed 5/6/7 PM slots. No reply since. Her pattern: usually responds within 2h. Worth a gentle nudge.
Drafted nudge
"hey Sneha, did you see my earlier message about qpi tech recruiter tomorrow? totally fine if it's a no — just want to lock it in either way."
Sneha T · Jenny said reject
Qpi Tech Recruiter · feedback to send to Sneha
Jenny's verdict · WhatsApp
"Solid candidate, very polished. But we want someone more hands-on / scrappy for this stage of the company. Not the right fit right now."
Drafted rejection feedback
To Sneha
"hey Sneha, thanks for taking the time for the qpi interview. they really liked you — feedback was you're polished + experienced, but they're looking for someone more hands-on/scrappy for this stage. honest feedback so you know what to look for next. happy to keep you in mind for similar roles. take care."
Rohan K · interview ended 17:55
StagBuzz Marketing · 25 min · feedback ready to send
Reminder: Tanvi prefers email now. These drafts go via email, not WhatsApp.
Drafted feedback prompts
To Tanvi (StagBuzz)
"Hi Tanvi, how did the Rohan K interview go? Want to know if you'd like to schedule round 2 or if there's any specific feedback to share with him. Will wait for your nod before moving him forward."
To Rohan
"hey Rohan, hope the StagBuzz interview went well today. they typically share feedback in 1-2 days — will pass along once I hear back."
Aman R · round 2 scheduling
Qpi Tech Recruiter · Jenny: advance
Jenny said · 11:42 AM
"Aman was strong. Set up round 2 with Akshay + the panel — same week if possible. He's our top candidate now."
Panel for round 2: Akshay + Tarun + Pooja (seeded in Pyjama panelists for Tech Recruiter). I don't have their Thu/Fri availability. Drafted (1) a holding reply to Aman and (2) a question to all three panelists asking what slots work for a 45-min round 2 this week.
Drafted · holding reply to Aman
"Aman! Jenny loved the chat. round 2 incoming — checking with their panel on slots this week. back to you within the day."
Drafted · panel availability ask (to Akshay, Tarun, Pooja)
"hey panel, Aman cleared round 1 with Jenny. need a 45-min round 2 this week (Thu or Fri) with the 3 of you. what slots work? happy to slot whenever overlaps."
Priya M · "let me check"
Qpi Tech Recruiter · 14:00 interview today
Priya replied 2h ago: "let me check, will get back in an hour." Her pattern: usually does get back. Wait recommended. Or send a soft nudge.
1
Priya M
91% fit
Tap to open full drawer · status, app answers, comms history
Optional soft nudge
"Priya gentle ping — interview is at 2 PM today, do you have an answer? happy to push if needed."
Krithika (Cupa) · 2 days no reply
Optimization Scientist status check
You asked Krithika 2 days ago: "any update on the 3 candidates we sent for Optimization Scientist?" No reply. Time for a re-ping.
Drafted re-ping
"hey Krithika, no rush but want to nudge — any thoughts on the 3 we sent for Opt Scientist? happy to send more if these aren't the right shape."
Pratiksha (PaisaWise) · 1d no reply
Compliance Officer status
You asked Pratiksha yesterday: "is the Compliance Officer role still active? we have 3 strong applicants in pipeline." No reply. May have hired externally per the role page.
Drafted re-ping
"Pratiksha, quick one — is the Compliance Officer role still open? Heard you might have hired internally, just confirming so I can update our pipeline."
Aakash R · 3 days on slot proposal
Qpi Tech Recruiter · Wed slots pending
Aakash counter-proposed Wed 7 PM at 10:55 (auto-accepted). Then sent slot confirmation 10 min ago and... silence since. Probably busy at work. Worth a soft check-in tomorrow morning.
Drafted check-in
"hey Aakash quick check — are you locked in for Wed 7 PM? want to make sure Jenny + the panel are confirmed on your end too."
Cupa
8 roles · 1 paused · Krithika, Riya
Relationship signal
Krithika last talked: 2d ago (no reply since). Riya: last Fri. Yusuf billing: just confirmed hired April 15.
Open roles
Optimization Scientist
stale
Krithika panelist · 2d no status update
9 Applied · 3 AI Interview · 2 Move Ahead · 4 Rejected
Backend Engineer
paused 2 weeks
Paused today by Krithika
11 Applied · 4 in pipeline · pause noted
Designer
focus
Krithika focused here per pause msg · pipe ramp-up
7 Applied · 1 Move Ahead
DevOps Engineer
active
Riya panelist · slow
5 Applied · 1 AI Interview
StagBuzz
5 roles · email-preferred · Tanvi, Saurabh
Relationship signal
Tanvi last talked: 9:32 AM today (email preference switch). Saurabh: last Wed. Rohan K interview today at 17:30.
Email-preferred client as of today. All candidate comms for StagBuzz now go via email. WhatsApp is for HM-to-Suchal direct only.
Open roles
Marketing Lead
active
Tanvi panelist · Rohan K interview today
8 Applied · 2 AI Interview · 1 Move Ahead
Performance Marketer
active
Tanvi panelist
6 Applied · 1 AI Interview
Growth Designer
slow
Saurabh panelist
4 Applied · 0 active
EatCookJoy
3 roles · Devendra (CEO) · urgent · today's flag
Relationship signal
Devendra (founder-CEO) last talked: Today 14:38 (urgent Ops Lead by Monday). Pattern: messages ad-hoc, expects fast turnaround.
Active urgent1
Ops Lead by Monday
today 14:38
Devendra urgent ping. 3 candidates messaged. Awaiting replies.
→ open task
Open roles
Operations Lead
urgent
Devendra · multi-city rollout · by Monday
3 outreach sent · awaiting replies
Customer Success
active
Devendra · slow burn
5 Applied · 1 Move Ahead
Optimization Scientist
Krithika panelist · stale 2d
Needs your action1
Krithika hasn't replied · 2d
stale
Status check on 3 candidates sent. Re-ping drafted.
Sumeet J
#PHR-2201
waiting on HM
Nisha A
#PHR-2189
waiting on HM
Karthik V
#PHR-2167
waiting on HM
iOS Engineer
slow burn · 1 interview/wk
Quiet role. No pending actions. Last interview was Wed; outcome captured.
Aarav P
#PHR-2050
scheduled
Risk Engineer
Akshat panelist · today's 1 PM interview
Needs your action1
Mohammed I · reschedule request
17 min
Daughter sick. Drafted holding reply + ask to Akshat for Thu slots.
Mohammed I
#PHR-3045
rescheduling
Divya R
#PHR-3022
confirmed
Backend Engineer · paused
Krithika paused 2 weeks · today 13:15
Paused today. Krithika asked for 2-week pause to focus on Designer. PyjamaHR updated. Daily candidate-pipe paused. Existing 4 pipeline candidates retained, no messages sent.
Pipeline frozen
Compliance Officer
Pratiksha · may be hired externally
Needs your action1
Pratiksha hasn't confirmed status · 1d
stale
Rumour: hired Vikash externally. Pinged Pratiksha yesterday, no reply. Re-ping drafted.
If externally hired, mark role closed + invoice fee discussion with Akshat.
Senior Product Designer
Akshat panelist · slow
Slow role, no pending actions. 2 interviews scheduled next week.
Riya M
#PHR-3098
scheduled
Task detail
Drilling in to this item
Item opened. This is the generic detail page that catches any inbox/list item that doesn't have its own dedicated screen yet. In a real product, this would show the full task context, drafted action, history, and a CTA. For the prototype: consider this a placeholder so no click is ever dead.