Your clients ask for work in their portal. Your team takes it on, makes it and sends it.
A client you look after opens Requests in their own portal, says what they need, adds files and a date, and sends it to their account team. Your team works every client’s requests from one list, the soonest needed first: take one, ask the client what it needs, make the work in their account, and the request is done when the work goes out. Five levels and a reach decide who on your team sees which clients, and what they may do.
Illustration · a sample agency’s Requests, with four requests from four clients
Priya wanted a Black Friday email. She asked once, answered one question, and it went out on the Friday.
One request, followed from the client’s portal to the send, on a sample workspace. The agency, its team and the flower shop are characters.
Ashby Flowers is a flower shop in Harrogate. Harbour & Finch looks after its email and its website, so Priya Shah, who owns the shop, never logs in to build anything. On a Monday she opens Requests in her portal.
The ask
She chooses Email, writes Our Black Friday email to everyone on the main list, adds the offer and two photos of wreaths, sets Needed by to Wednesday, and presses Send to your account team. The request opens, marked New.
Taken, and one question
At Harbour & Finch it lands under Not taken. Sam, who makes the agency’s emails, presses Take it, and Priya sees Being made by Sam Patel. He has one question, so he writes it as Ask the customer: should the code work in the shop too? The request moves to Waiting on you in Priya’s portal, she is emailed from the agency’s own address, and its clock stops until she answers. A Team note reminds Sam which brand preset to use; Priya never sees it.
Made, added, done
Priya answers from the email’s link. Sam presses Make it in Campaigns, builds the email in Ashby Flowers’ own account, and adds it under Work so Priya can follow it. When he schedules it for Friday morning, the request is done by itself.
Priya asked once, answered one question, and saw it being made. No call, no email chain, nothing lost.
Who saw what
Mia, Ashby Flowers’ account manager, saw it all under Mine. Claire, who owns the agency, saw Requests to make in Customers. Ruth, a viewer on the North branch, could read the request and change nothing.
That is one request from one client. Every client you look after asks the same way, and your team works them all from one list, under your name.
Every client’s requests, on one list your team works from.
This is your dashboard’s Requests, on a sample agency.
- Open, Waiting on the customer, Not taken, Mine and Done.
- Each request with its client, the date it’s needed by, who has it and the time on the clock.
- Late is marked once the day has passed.
- New request adds one for a client who asked by phone or email.
One form, in their own portal.
What kind of work: Email, Landing page, Website, Sequence, Social post, Ad, Print, Film or Something else. What they need in a line, anything you should know, up to 20 files of up to 50 MB each, and the date it’s needed by.
They follow it on the request itself: who has it, each message from the account team, and each piece of work as it’s made. They answer questions there, move the date, withdraw it, or open it again.
- Nine kinds of work, and files
- Followed on the request
- Answered in one place
Illustration · a client asking for work in their portal
Our Black Friday email to everyone on the main list: 20% off wreaths, Friday to Monday. Photos attached.
Should the code work in the shop too, or online only?
Use the red preset; the green one is for spring.
Illustration · one request opened, with a question for the client and a team note
Take it, ask, make it, and it’s done when it goes out.
Take it, so the client and your team know who’s making it. Reply to the client, Ask the customer when you need something, or leave a Team note the client never sees. Make it in opens the right place in the client’s account.
Add work links what you made to the request. When every piece goes out, a campaign scheduled or sent, a page or website published, a sequence turned on, a post scheduled, a film ready, the request is done by itself. Mark done covers an ad or print.
- Take it, or take it from someone
- Questions that stop the clock
- Done when the work goes out
The soonest needed first, and the time it’s really been with you.
The Clock counts the time a request has been with your team: weekdays only, in your own time zone, so a Friday afternoon request isn’t three days old on Monday. It stops while the request waits on the client, and once it’s done.
In Customers, the Status filter’s Requests to make shows every client with work waiting on your team, and each one’s row says how many, and whether one is late or not taken yet.
- Weekdays, in your time zone
- Stopped while waiting on the client
- Late and not taken, flagged
Illustration · a sample agency’s customers with requests to make
Illustration · a sample agency’s team, with five levels and their reach
Each person sees the clients they work on, and does what their level does.
Owner, Manager, Account Manager, Production and Viewer, each with a reach: every customer, chosen branches, or only the customers they’re put on. Each person’s menu shows only what their level uses.
Rename the levels in your agency’s own words. Owners choose whether account managers add new customers, and whether production sends what it makes and sees who the contacts are. Billing is given by an owner, person by person.
- Owner to Viewer
- Every customer, branches, or their own
- Levels in your own words
Who runs it, who stands in, and who makes the work.
Each client has an account manager, a backup who stands in, cover until a date you choose while someone is away, and production: a person, or a pool that takes the work for its clients.
A request’s emails go to whoever has it, or whoever covers them; with nobody on it, to the client’s account team; with no account team, to your owners and managers who look after every customer. Nobody is emailed about what they did themselves.
- Account manager and backup
- Cover while someone is away
- Production people and pools
Illustration · a client’s account team, on a sample agency
A client portal and a production queue your agency would otherwise piece together from several tools, under your name.
Each line is in the one plan, for every client you bring. On the right, the kind of tool a business usually pays for to get the same job done.
| In SendTo | Instead of |
|---|---|
| Requests in every client’s own portal | A client portal app |
| One list of every client’s work, with a clock | A project management tool |
| Questions, replies and team notes on the request | Email chains and a chat app |
| Done when the work goes out | Someone ticking boxes |
| Five levels, branches, pools and cover | An enterprise plan for roles |
| Your name and logo on every screen your client sees | A custom build |
| Every client you look after | One flat fee |
What you might be thinking, answered straight.
“Our clients just email us.”
They still can. Add the request for them with New request, so it’s tracked with the rest, and the next time they can ask in their own portal.
“I don’t want clients seeing our internal notes.”
A Team note is for your team only. The client never sees it, or its files.
“How do I know what’s late?”
Every request has Needed by, marked late once the day has passed, and Customers shows every client with requests to make.
“Our designers shouldn’t send.”
Turn off Send what they make for production, and someone else sends.
“Do my clients ever see the SendTo name?”
No. Your clients ask at your portal, under your logo, and their request emails come from your own sending domain.
“I want to see it before I decide.”
Open the account: no card, and a sample workspace is ready when you confirm your email. Add a managed client and Requests appears.
Agency teams and Requests, answered
Who can ask for work?
A client’s Admins and Editors ask, write on requests, change their dates and withdraw them. Their Approvers and Viewers read every request and change nothing.
Does every client get Requests?
Every client you look after. A self-serve client makes their own work, so there’s nothing to ask for.
Where is it on my side?
Requests, under Partner, after Customers. It appears once you look after a managed client.
What can a client ask for?
Email, Landing page, Website, Sequence, Social post, Ad, Print, Film or Something else, with up to 20 files of up to 50 MB each.
When is a request done?
By itself, once every piece of its work goes out. For an ad, print or anything else, press Mark done. If a piece goes back to draft, the request opens again.
What does the clock count?
Weekdays only, in your own time zone, while the request is with your team. It stops while it waits on the client.
Who is emailed?
Whoever a request waits on. Your team’s emails open the request; the client’s come from your own sending domain, in your brand. Nobody is emailed about what they did themselves.
Can a client reply by email?
Not onto the request yet: the email’s link opens the request, and they answer there.
What are the five levels?
Owner, Manager, Account Manager, Production and Viewer, each with a reach: every customer, chosen branches, or only the customers they’re put on. You can rename them.
Do my clients ever see the SendTo name?
No. Your clients ask at your portal, under your logo, and their emails come from your own sending domain.
Do I need a card to try it?
No. Create your account and a sample workspace is ready when you confirm your email. Sending switches on when you activate.
Agency teams and Requests, and everything else in the hub, on one platform under your name.
Every client you look after can ask for their work in their own portal, and your team makes it from one list, each person seeing the clients they work on. Open your account free and look around a sample workspace.
No contract · Cancel any time · Explore everything before you pay