Form management for agencies with many client sites
Form management for an agency works best from one workspace with a separate client for each customer. Each client's forms, submissions and emails stay apart, your team sees all of them from one Inbox, and each client can have a login that shows only their own requests. SagePigeon is built around that model. Below is how it fits together, what a client can and cannot do, and which plan a typical agency needs.
The usual mess
Forms usually arrive with the site: one per client, set up by whoever built it. A WordPress plugin here, a builder's own form there, notifications going to a client address nobody at the agency can see. When a client asks "did that enquiry from Tuesday come through?", someone has to log in to their site, or their inbox, or ask them to forward it.
The fix is to send every client's forms to one place you control, and still keep each client's work separate.
One workspace, a client per customer
When you create a SagePigeon workspace, choose Clients I manage as who it is for. You can add your first client on the same screen; Save and open clients takes you to the Clients page.
From there, Add a client for each customer. A client holds its forms, the submissions they receive and the emails they produce. Within a client, you can file forms into groups, one per website for example. Groups are only for tidiness and do not change who can see anything.
When you make a form, choose which client owns it. That choice decides who can see the form and everything it receives. Point the client's website form at the form's endpoint, and submissions start arriving under that client.
A workspace holds up to 500 clients. The number of forms depends on your plan.
What your team sees
Your own team sees every client. The Forms page lists forms grouped by client and site, each with how long its oldest unanswered request has waited, so the client who is being kept waiting stands out. The Inbox works across all clients, oldest first, or narrowed to one.
Each request has a clock that runs until someone replies, and the Overview opens by naming who is waiting longest. For an agency the clock has a second use. When a client says enquiries go unanswered, you can show them the times. Contact form leads lost in a shared inbox explains how the clock works.
A login for each client
Client logins work on every plan, and each one takes a seat. Free has a single seat, which is the owner's, so in practice you need Pro (10 seats) or Scale (100) before you can invite a client. Seats are shared between your team and your clients' logins.
To invite someone from the client's side, open Settings → Team and press Invite someone. Give them the Client viewer role and limit it to their client. The invitation link works for 14 days, and it holds a seat until it is accepted or withdrawn.
A client viewer gets a narrow, useful view: their own Overview, Inbox, forms, email log and response times. They can:
- read every submission their forms receive;
- reply to their own customers from the Inbox, which stops the clock;
- add their own Slack, Teams or other chat destinations to their forms, up to 5 per form, within what your plan allows;
- set up a summary email, sent to themselves only;
- reword their own notification and auto-response emails.
They cannot change a form's fields, routing or recipients, and they never see another client's work. Your team's settings stay hidden too: webhook and captcha secrets are removed from what their login receives, and the addresses of chat destinations your team set up are blanked. They can see that your agency manages those destinations, without seeing where they point.
The server enforces all of this. Lists, search and exports only ever return a client login's own records, and a request for another client's form is refused, whatever the browser sends.
Templates a client writes are cleaned before they are saved, because an auto-response goes from your verified domain to whoever filled in the form. Anything that could run in an email is stripped, and SagePigeon tells them what it removed.
History stays with the right client
Agencies reorganise. A form moves from one client to another, or a client is split in two. In SagePigeon, each submission records which client received it at the moment it arrived, and that never changes. Move a form to a new client and its future submissions go to the new client, while last year's enquiries stay with the client who received them.
Integrations per client
Each form has its own integrations, so each client can have its own Slack channel, its own Google Sheet or its own webhook into its CRM. If you hand out API keys, a key can be limited to one client. It then sees and sends only that client's data.
Which plan an agency needs
Plans are priced by submissions and forms; the number of clients does not change the price. A worked example, as an illustration rather than a real customer:
An agency runs 12 client sites with 2 forms each: 24 forms. Together they receive about 1,800 submissions a month. Two people at the agency answer enquiries.
That fits Pro: 50 forms, 5,000 submissions a month and 10 seats, for $49 a month or $490 a year. Two seats go to the agency, which leaves 8 for client logins. Past 5,000 submissions in a month, Pro carries on at 1¢ each instead of refusing them, as long as you leave that switched on in Billing.
Free allows 3 forms and one seat, which suits trying SagePigeon on your own site and not much more. With one seat there is no room for a client login.
Scale is for agencies past 50 forms or 10 seats. It includes 500 forms, 100 seats, 50,000 submissions a month, file uploads up to 25 MB, 20,000 Email API sends a day and two years of history, for $149 a month or $1,490 a year. Volume can tip the decision too. At 15,000 submissions in a month, Pro costs $49 plus 10,000 × 1¢, which is $149, the same as Scale. Above that, Scale is cheaper.
One subscription covers every client in the workspace. SagePigeon does not bill your clients; how you charge them is up to you.
Getting started
- Create a workspace and choose Clients I manage.
- Add your first client and make a form under it.
- Change the client's website form to post to the new endpoint, and send a test submission from the form's Setup tab.
- Add a Slack destination for your team's channel. On Pro or Scale, invite the client when they are ready.
Questions people ask
Can a client see another client's submissions?
No. A client viewer login is limited to the clients or forms you choose, and the server checks that on every request, including search, exports and replies.
What happens to old submissions if I move a form to a different client?
They stay with the client that received them. Each submission records its client when it arrives, so moving a form does not move its history.
Can clients change their own forms?
A client viewer cannot change a form's fields, routing or recipients. They can reply to their own customers, and add their own Slack or other chat destinations and a summary email to themselves. Invite someone as a member if they should edit forms.
Does each client need its own SagePigeon account and plan?
No. Clients live inside your workspace, and one subscription covers all of them. Your plan's form and submission allowances are shared across every client.