Contact form leads lost in a shared inbox
Contact form leads get lost in a shared inbox because the inbox can tell you an email arrived and cannot tell you whether anyone answered it. Every notification looks the same, nobody can see who picked one up, and Saturday's enquiry is on page two by Monday. The fix is to track each request until a person replies: who is waiting, who has it, and how long it has been. Below is when a shared inbox is fine, when it stops working, and how SagePigeon's reply clock handles the gap.
When a shared inbox is fine
If one person reads every enquiry and answers within the day, keep the shared inbox. You do not need a tool to coordinate with yourself, and a handful of messages a week will not get buried. Add a filter so form notifications get a label, and move on.
It also works for a small team with a strict rota, where Monday belongs to Sam and Tuesday to Dana and everybody sticks to it.
When it stops working
The trouble starts with the second person.
Everyone assumes someone else replied. Dana sees the email, means to answer after lunch, and then sees it has been read. Sam read it too, and also thought Dana had it. Neither replied.
Weekends. An enquiry that arrives on Saturday afternoon sits under Sunday's newsletters and Monday's invoices. By the time somebody scrolls down to it, the customer has booked elsewhere and never tells you why.
Nobody knows how slow you are. Ask a team how long it takes to answer a website enquiry and you will hear "same day, usually". Nobody has measured it, because the inbox does not measure it.
None of these produce an error. The form worked and the email was delivered, so nobody goes looking.
What a reply clock does
SagePigeon starts a clock on every submission the moment it arrives, and the clock runs until someone on your team replies to the person who wrote in.
The Overview opens with a sentence about the people waiting, for example "Five people are waiting for a reply, and nobody has picked any of them up yet. Two have waited more than a day." Each part of that sentence links into the Inbox.
The Inbox opens on the person who has waited longest. From the request you can press Take it on, which puts your name on it so the rest of the team can see it is handled, or Assign to… a colleague. Write in the Write a reply box and press Send reply. The email goes to the customer under your form's name, and the clock stops.
If a request waits more than 24 hours with no reply, SagePigeon emails the workspace's owners and admins once a day with the list, unowned requests first, each with how long it has waited. A request is listed once, so a standing backlog does not become a daily nag. Anyone who would rather not get it can turn off Requests nobody has replied to under Settings.
The Response times page turns the clock into numbers: the median wait, the slowest reply, and how many were answered within an hour and within a day. The slowest reply is the figure to watch. A two-day wait on one wedding enquiry costs more than a good average makes up for.
Replying from your own mail
Your team already has an inbox, and on Pro and Scale they can keep working in it.
Each notification on those plans carries a private reply address. Hit reply in Gmail, Outlook or Apple Mail and write as normal. Your reply goes to SagePigeon, which stores it on the request, stops the clock, strips the quoted history, and sends it on to the customer from your form. When the customer answers, their reply comes back to the same request, so the whole conversation sits in one place.
On the Free plan, the notification's Reply-To is the customer's own address. Replying from your mail still reaches them, but SagePigeon never sees it, so the clock keeps running. If you are on Free and want the clock to be right, reply from the Inbox.
What counts as an answer
SagePigeon counts the first reply from anyone other than the person who filled in the form. Customers often reply to the automatic "thanks, we got your message" email, and if their own reply counted, every request would look answered in seconds.
The notification email being delivered does not count either. Delivered means the email reached your inbox. Answered means a person wrote back.
Setting it up for a team
- Create a workspace and choose My team when it asks who the workspace is for.
- Make a form and point your site's form at its endpoint. The static site guide has the snippet.
- Invite the people who answer enquiries from Settings → Team. The Free plan has one seat; Pro has 10 and Scale 100.
- Send a test submission from the form's Setup tab and watch it go from stored to sent to waiting.
- If your team lives in Slack, add a Slack destination so the alert lands there too. See Send website form submissions to Slack.
Slack is a good place to hear about a request. Keep the record in SagePigeon, though, because a Slack thread cannot tell you whether the customer got an answer.
Where a CRM fits
SagePigeon is not a CRM. A CRM is for deals with stages and values, and it is the right tool once a lead becomes an opportunity. SagePigeon covers the stretch before that: from the moment someone presses Send on your website to the moment a person writes back. If your sales team works in a CRM, send each submission on with a webhook once SagePigeon has it.
What it costs
The Inbox, Take it on, replies sent from the Inbox, the Response times page and the daily nudge all work on Free, which covers 500 submissions a month and 3 forms for one person. Threading replies from your own mail needs Pro at $49 a month, which also adds 10 seats, routing rules that send each request to the right person, and auto-responses. See pricing for everything else on each plan.
Questions people ask
What counts as a reply?
The first reply from anyone other than the person who filled in the form. A reply sent from SagePigeon's Inbox counts on every plan. On Pro and Scale, a reply sent from your own Gmail or Outlook to the notification counts too. Auto-responses do not.
Do I have to reply from inside SagePigeon?
On Pro and Scale, no. Reply to the notification email from your usual mail app; the reply goes to the customer and is threaded onto the request. On Free, reply from the Inbox so SagePigeon can see it.
Who gets the reminder about unanswered requests?
The workspace's owners and admins, once a day, listing requests that have waited more than 24 hours. Each request is listed once. It is on every plan, including Free, and can be turned off under Settings.
Does the customer see SagePigeon?
Replies go out under your form's name, from your verified sending domain if you have set one up on Pro or Scale.