The info@ inbox nobody owns

The info@ inbox nobody owns is the shared address a UK firm puts on its website and then leaves for whoever is free. A new enquiry can sit there until the customer writes again, or two people can answer it on the same morning. The fix is a tracked queue, where each enquiry has one named owner and a reply time the whole team can see.

What a shared inbox does not record

A shared mailbox is where mail arrives. It can show that a person wrote. It doesn't name who will answer, or the time that answer is due.

The info@ inbox nobody owns can fail in a dull way. Several people can see the message, and none of them is responsible for it. A Friday enquiry can sit until Monday because each person thinks the other has it. The customer then writes again, so the firm has two threads for one job. Or both people reply, and the two answers don't agree.

You can search for the sender. You can't open a list of enquiries still waiting, with a name against each one. A folder can remind someone to look. It still doesn't record an owner or a reply time.

What a tracked queue adds

A tracked queue is a list of enquiries, not a new place to write email. Each row keeps the message that came in, a status, the person handling it, and the time a reply is due. One person takes the row. The rest of the team can see that it is taken.

The answer can still leave as ordinary email. Open work is visible before anyone opens a thread. An internal portal is that same list in a browser the staff already use: a login and the queue, with a note of what you told the customer. The customer doesn't need an account for this step.

The queue's job ends once the reply has gone. What happens after someone has answered is a different problem, which I've covered in Quotes and invoices stuck in email. An enquiry with an owner can still end as a PDF the office can't match to the job a month later.

Shared inbox versus a tracked queue

• Where it sits: Shared inbox: a mailbox several people can open. Tracked queue: a row on a list.
• Owner: Shared inbox: no name, unless someone says they have it. Tracked queue: one person on the row.
• Reply time: Shared inbox: when somebody notices. Tracked queue: a due time visible without opening the thread.
• Two replies: Shared inbox: two people can send. Tracked queue: the second person can see the row is owned.
• After the answer: Neither stores the quote you agreed. That needs its own record.

When the enquiry starts on your website

Trade and service firms can keep website enquiries in TradeOps, in the same system as customers and quotes. The lead list stores the topic from the form, the customer's message, contact details, a status, the person handling it, and notes. Statuses listed there include new, contacted, quoted, won and lost. A phone call or a referral can be typed in, with the source recorded.

A team member picks the enquiry up, writes the notes, then creates a customer and starts a quote. Those details carry across. The form and the office tools are one platform, so the enquiry doesn't have to be copied out of an email. Roles decide who can view the list and who can change it.

That list covers form enquiries and ones you type in. It doesn't describe collecting mail from a shared info@ address. If the mailbox is still where new work arrives, point people at the form, or build a queue for the mail.

A fixed price for one release

When TradeOps is the wrong shape, we build the queue as software on your own accounts. A scoping conversation is free. You say where enquiries land and who should own a reply. We send a written scope, and billing starts only once you agree it.

Scoped software is quoted at a fixed price for the release you agreed. A larger platform is quoted release by release, so a finished release is still useful if you stop. Later releases are priced separately. For a small or medium business, that first release is priced as one number. There is no universal price list.

You own the code. The repositories and the cloud accounts are in your name from the start, and we work in them. The engineer who scoped the work stays responsible through delivery and after launch. Delivered work is covered for twelve months. After that, support is a separate retainer, or you run the system from the documentation.

The SaaS studio builds internal tools of this kind in your repository and your cloud account, and a customer portal if you want one later. Software development is where we scope that first release. Whether your customers should have a login is covered separately in Customer portal vs email-and-Excel.

If new work is disappearing into a shared address, talk to an engineer. Say where enquiries arrive and who is meant to answer them. You'll get a written price before any billing starts.