Chat
Every direct message your connected accounts receive lands in one inbox — Instagram, Messenger and WhatsApp side by side. Flows can answer the first message on their own, and hand the conversation to a person the moment it matters.
What arrives here
Chat covers the accounts you already connected — connect the account and messages start appearing, with no extra setup on Instagram or Facebook. WhatsApp is the one exception, and the section below covers it.
- Instagram — direct messages, story replies and button taps, on accounts connected with Instagram Login. Via Facebook the permissions are still with Meta; the connect screen says which capabilities each method has right now.
- Messenger — messages sent to a connected Facebook Page.
- WhatsApp — messages to your WhatsApp Business number, once you finish the extra step below.
The reply window
Every one of these platforms only lets you answer for 24 hours after the person's last message. That is their rule, not ours, and PostRite shows the clock in the conversation so nobody writes a reply that cannot be sent.
- Inside the window, reply freely.
- Outside it, the composer explains why and waits — the contact has to write again first.
- A conversation that started from a comment never had a window. You can still answer it by hand, once — the same single private reply the automation would use.
- On WhatsApp only, an approved message template can reopen the conversation.
Receiving WhatsApp messages
WhatsApp runs on your own Meta app, so we cannot switch receiving on for you. Sending works from the moment you connect; receiving needs three values copied across once.
- Open the WhatsApp account in Platforms and copy the callback URL and verify token PostRite shows you.
- In your Meta app, paste both into the WhatsApp webhook settings and subscribe to messages.
- Paste your app secret back into PostRite so we can verify that the messages really came from Meta.
Until the app secret is set, the WhatsApp account stays send-only and the card says so.
Flows
A flow answers on its own. You build it as a small map of steps: send a message, wait, offer buttons, branch on the answer, tag the contact, or hand over to a person.
- Start it on a keyword, on someone's very first message, on a story reply, or on a comment — the classic "comment a word, get a DM".
- Offer buttons and send each answer down its own path.
- Tag people as they go through, and check those tags later to decide what to say.
- End with a handoff whenever a human should take it from there.
You will find them behind Flows at the top of the inbox, and a link back to the inbox at the top of the builder.
How many flows a workspace can have depends on your plan — the pricing page lists the number for each. Nothing is deleted if you move to a smaller plan; flows beyond it simply stop answering, and say so in their history, until you upgrade again.
Comment a word, get a DM
This is the flow most people want, and it has its own settings under Trigger next to the builder:
- Pick any post or one specific published post, chosen from your own feed with its thumbnail.
- Add the keywords that should set it off, and how to match them — contains, exact, or starts with.
- Add a Reply to comment step to answer publicly, with up to five different wordings so a busy post does not repeat itself word for word.
- Then send the direct message — it reaches people who commented but never wrote to you, which is the one case the platforms allow.
The direct message is a one-time opening: the platforms allow a single private reply per comment, and only for about a week after it was written. After that the usual reply window applies — if the person never answers, the flow says so in its history instead of writing into a closed conversation.
Guardrails
- One flow per message — two rules never answer the same "hi".
- A cooldown and a daily cap, both per contact, so nobody is answered in a loop.
- A step limit, so a menu that loops back on itself still stops.
- A run history that records the runs which did nothing, and why — that is the answer to "my flow did not reply".
- A post with its own auto-reply switched on answers those comments itself, so a comment flow steps aside there — and its history says why.
Taking over
Pausing automation on a conversation stops every flow in it immediately, and no new one starts while it is paused. It is the switch to flip the moment a person needs to answer instead.
Closing a conversation tidies it out of the list and you can reopen it whenever you like. Deleting one is separate and permanent — it removes the contact, every message and the automation history, so it is there for spam or for someone asking to be forgotten. Admins and owners only.