One calendar, every department
Coordinate Testimonial Requests Across Teams
When four departments all want testimonials, the problem is not only asking the same customer twice. It is everyone asking in the same fortnight, then nobody asking for two months. A shared request calendar gives each team a window and a deadline. Pick when your quarter starts to lay one out.
- A request window for each department
- A quarter-long plan with dates
- Bulk sends kept apart from one-to-one asks
The problem, solved
What uncoordinated departments do to a quarter
Every team asks at quarter end
Sales wants proof for the last push, marketing for the next campaign, success for renewals. Customers get three emails in one week.
With StoryProof: Give each department its own window on a shared calendar, and keep the customers it plans to ask as contacts in one StoryProof space.
The monthly email allowance runs out early
One bulk campaign uses most of the month’s request emails, and support cannot send any after a great ticket.
With StoryProof: Review request emails per month depend on the plan. Divide the allowance between windows before the quarter starts.
Nobody knows which team sent what
A testimonial arrives and nobody can say which department’s request produced it.
With StoryProof: Tag contacts with the department and the window when the request goes out. Tags are on every plan.
Reminders spill into the next team’s window
Manual reminders from one department go out while the next department is already asking.
With StoryProof: From Pro, follow-ups run on a fixed schedule over about a week and stop when the customer replies, so each window has a predictable tail.
Each department uses its own tool
A request from a CRM sequence, a help desk macro and a newsletter tool cannot be put on one calendar.
With StoryProof: Send every request from the same space, by email only. Seats per space depend on your plan, so give one sender per department a seat.
Flip the switch to see how StoryProof handles each one.
Rules for the calendar
In StoryProof
Run the calendar in StoryProof
- You will need
- One sender named per department
- A quarter start date everyone agrees
- 1
Give each sender a seat
Add one person per department to the same space, within your plan’s seat count.
- 2
Load each department’s list as contacts
Bring in the customers each team plans to ask, and tag them with the department and quarter.
- 3
Send only inside the window
Each sender emails their list in their window. Keep an eye on the monthly request email allowance.
- 4
Work the queue in the quiet period
Nothing is public until approved, so use the quiet weeks to approve, decline or follow up.
What happens next: Keep last quarter’s calendar next to the new one. If one window produces little, move it rather than adding a second.
Before you start
What the calendar cannot enforce
No scheduling of windows in the product
StoryProof is not described here as locking a department out of sending. Windows are a team agreement.
One allowance for the whole account
Request emails per month are counted per plan, not per department. Splitting them is up to you.
Tags rely on the sender
If a sender skips the department tag, the joint review will miscount.
Requests outside StoryProof are invisible
An ask made on a call or in a chat app does not appear anywhere unless someone tags the contact afterwards.
FAQ
Questions people ask
Short answers to what usually comes up next.
Which department should go first?
Whichever asks the most personal, one-to-one requests. Bulk sends are easier to trim around the customers already asked than the other way round.
How long should each window be?
Two weeks is enough for one-to-one asks plus their reminders. Shorter windows tend to overlap once reminders run.
Is this different from a content calendar?
Yes. A content calendar decides when testimonials are published. This calendar decides when they are requested and by whom.
What if one team needs testimonials urgently?
Ask the team whose window it is to include the request on their behalf. That keeps one sender per customer per window.
Still have a question? Ask the StoryProof team or book a demo.
Put every department on one calendar
Send requests from one shared StoryProof space, tagged by team, so the quarter is planned rather than crowded.
Last updated 2026-11-17.