Set up and troubleshoot one free incoming-DM keyword reply. This practical test is separate from the complete free-plan overview: choose HOURS, write your actual opening-hours answer and verify the result.
Illustrative wording, not a captured send. Replace the placeholder with your real information. This written reply does not use AI generation or collect a completed lead.
Match a configured word or phrase in an incoming DM and attempt the written response. Test the wording your customers actually use.
Check whether the event matched and the send succeeded. Missing permissions, account restrictions or a closed window can prevent delivery.
Pause automated replies with the available takeover control when a person should answer. Local pause does not assign a team agent or transfer Meta thread ownership.
An incoming HOURS keyword receives the hours you supplied; no invented business details.
Check the exact incoming text, enabled rule and send result before changing the response.
Use a new incoming DM rather than a comment for this test, so you can isolate DM matching from the separate comment private-reply path. Confirm the received text matches the rule and that the reply reaches the same conversation.
If no reply arrives, check the connection and required permissions, the one-active-rule limit, free credit availability and recipient restrictions. Read the message result rather than relying on a public acknowledgement.
You can test one active automation across all channels on Free, with one Instagram account, 300-character DMs and a Repli footer. The free allowance starts with 15 signup credits plus 5 daily credits; it is not unlimited daily delivery.
It isolates the incoming-DM keyword workflow. Comment-to-DM has separate initial private-reply restrictions and its own setup guide.
No. Ordinary automated DMs require an eligible conversation. Ongoing sends must respect Meta’s 24-hour window; comment private replies have separate restrictions.
No response-time or account-safety guarantee is offered. Repli uses the official API, but provider event delays, permissions, restrictions and sending limits still apply.
Pricing · All features · How it works · Blog