What's new in PostEngage

Talk to the founder without leaving PostEngage. Share screenshots too; every image is checked before it's shown.

Moving to a bigger plan mid-month now charges the prorated difference, and your extra credits land straight away.

USD everywhere, INR in India.

Get told the moment Instagram access expires or a permission is missing, before replies stop.

A rebuilt platform: safety checks on every reply, held replies with reasons, voice learning, and a new dashboard.

Rebuilt from the ground up: one API instead of five services that disagreed about ports and cookies, Postgres instead of Mongo, and a policy gate that every outbound message passes through rather than three code paths that each decided for themselves. What that is worth to somebody using it comes down to four things.

1. Every refusal has a reason you can read. Ten checks run before a reply is drafted, in a fixed order, and the one that stopped a send is recorded with the sentence explaining it. The old build recorded that a send failed.
2. Templated replies stopped costing anything. A credit is spent when the model writes something new. Your own written template goes out free, and unlimited, including when your credits are gone.
3. Takeover is structural. The moment you reply to a thread by hand, the automation stands down in it. It is a gate check, not a setting.
4. Nothing is metered per contact. One viral post does not produce a larger invoice.

Keyword monitoring feeding engagement triggers, and one dashboard covering both finding people and answering them.

v0.4.0

What was spent, broken down by day, week and month, so a bill stopped being a surprise at the end of it.

v0.3.2

Comments were being missed during traffic spikes, and reconnecting after an Instagram token expired needed a hand. Both fixed.

The missed-comments bug is the reason ingestion in the rebuild writes an event down before deciding anything about it, and deduplicates on a key rather than on timing. A retry can now arrive twice and reply once. The post on what a comment window actually is covers why the timing matters so much.

v0.3.1

Trigger-based direct messages, new-follower and story-mention triggers, and templates the model could rewrite in your own register.

v0.3.0

Every action the automation took, filterable by type, with the original comment beside the reply that went out.

This is the feature that became the most-used screen in the product, which is why the rebuild extends it rather than replacing it: the same view now lists what was refused, with the check that refused it. How that reads in practice.

v0.2.0

Instagram comment auto-reply, voice training from your own past replies, credit-based billing, and a dashboard.

Two decisions from that week survived every rewrite since: replies are priced per reply rather than per contact, and the voice is learned from things the account owner actually wrote rather than from a tone picker.

v0.1.0