Playbooks · 5 min read
Architecture Firms: Who Actually Owns the Instagram Inbox
The solo practitioner's problem is that most of the inbox is not work, and that post covers it. A studio has a different problem, and it is organisational rather than volumetric.
In most firms the Instagram account is run by whoever was interested. A junior who is good at photography. A marketing hire who joined last year. Sometimes an intern, for a summer, and then a different intern. The account posts finished project photography, it collects a respectable number of messages, and the question nobody has answered is what happens when one of those messages is a developer asking whether you take on hospitality work.
Automation does not fix that. It makes the consequences arrive faster.
The reply goes out under the name on your drawings
This is the thing to sit with before touching a builder screen.
A D2C brand can send a chirpy template and lose nothing. Your practice puts the same name on tender submissions, on stamped drawings, and on a competition entry that a jury will read. An automated reply is signed with that name, and the register it uses is a positioning decision whether or not anybody made it deliberately.
Somewhere between a warm reply and a professional one there is a sentence your practice would never put in an email. A template will send it anyway, four hundred times.
The practical consequence is that voice is not a nice-to-have here. Voice DNA is built from replies the account owner actually wrote — so the input matters. If the studio's Instagram replies were written by a rotating cast of interns over three years, that is not your practice's voice; it is an average of people who have since left. Before training anything, pick the replies a partner would be happy to see quoted back in a meeting, and use those.
We do not route to people, and you should plan for that
Here is the honest limitation, stated plainly, because a lot of writing about this pretends otherwise.
There is no assignment. No round-robin, no owner field, no "send hospitality enquiries to Nikhil", no CRM sync, no ticket queue. The inbox is shared. What exists is takeover: the moment any human replies by hand, automation stands down in that thread permanently.
That is a genuinely useful primitive and it is not a routing system. So the routing you need is a rota, not a setting — a human protocol agreed once and written down:
- One named person per week. Not a team, not "whoever sees it". A studio inbox with shared responsibility is an unread inbox, and this is true before automation and after it.
- A rule for what gets escalated same day. A named developer, an institutional client, a press enquiry, a competition invitation. Everything else can wait until the end of the day.
- A place enquiries go that is not Instagram. Export the leads CSV weekly into whatever the practice already uses. Nothing syncs on its own, so the export has to be somebody's recurring task or it does not happen.
- A partner reads the automated replies once a month. Not the volume. The actual text of what went out under the practice's name.
Three kinds of message that must never meet a template
Press and publication. A journalist on deadline, a magazine asking for drawings and a project credit list, a book editor. These have a shape a template cannot meet and a cost to getting wrong that is measured in years of coverage. Negative-keyword them out: press, publish, feature, interview, magazine, credits, high-res.
Recruitment, in both directions. Portfolios arrive constantly, and so do messages from people you might actually want. A generated reply to a good architect looking for a job is an unforced error, and the automated decline of a portfolio is worse in a firm than in a one-person practice because the sender assumes it was read by a studio.
Anything that mentions a dispute. A former client, a contractor, a neighbour objecting to something under construction. An automated reply attached to a live disagreement is a document. Route it to a partner and nowhere else.
What is safe is the practice, not the project
The automatable set for a firm is everything true about the studio regardless of who is asking. Where you are and what the studio hours are. The typologies you work in. Whether you take work outside your region. How an enquiry becomes a first meeting. Whether you host site visits. Where portfolios and vendor introductions should go instead. Which project a photograph is from and who the photographer was, since that is the single most common comment under good project photography.
What is never safe is anything about a specific project's cost, programme, fee, or feasibility. Those depend on scope, stage and site, and a figure sent by template is a figure the conversation will start from. Publish the mechanism — that fees are quoted after a first meeting, that work is staged — and leave the number to a person.
The costs and the edges
Templated replies are free and unlimited. A credit is spent only when the AI writes a new reply, so a firm running mostly practice-level templates spends very little. Free tier is 100 credits with no card; packs start at ₹499.
No calendar, so it never books a meeting. No CRM. No WhatsApp. No messaging anyone who has not written first. Official Instagram Graph API only, which means seven days to reply to a comment and twenty-four hours inside a DM thread — and that DM clock restarts only when they message again, so "our associate will get back to you next week" is a sentence that expires before it can be honoured.
Set the rota before the automation. Then read what stops a reply going out, and if the studio also runs consulting or advisory work alongside design, the consulting firms post covers that inbox shape.
