FIRST-FIVE READINESS
Prepare your Facebook Page pilot setup.
Use this checklist before pilot review or an invited setup. It helps your operator gather the right access and information without connecting an account.
Before pilot review
- Choose one business, one accountable operator and one Facebook Page that receives recurring public comments.
- Confirm the operator manages that Page and can complete Facebook authorization with their own account. Do not share a password or access token.
- Collect current hours, services, common questions, approved links and the topics that must stay with a person.
- Plan for the operator to read the original comment and review every draft before deciding whether to post it.
After you receive an invitation
- Open the invited setup link and sign in with the Social Response Agent customer account that received access.
- When Facebook opens, use the personal Facebook account that manages the invited Page and select that exact Page.
- If the Page is missing or a different Page appears, stop. Do not connect another Page to work around the issue; use the missing-Page guidance in Help.
- Return to setup, confirm the Page name, then add the business facts and reply boundaries you prepared.
Set the operator’s reply boundaries
- Keep Approved business knowledge limited to confirmed public facts and operator-approved links. Do not add passwords, customer records, payment details or private conversation history.
- Write down the topics that must stay with a person before reviewing live comments. Hold account-specific order or payment issues, refund disputes, threats, legal or medical questions, safety concerns, exposed private information and any fact you cannot confirm.
- For a public comment that needs private help, do not ask for personal details in the thread. If appropriate, edit the draft to point only to the business’s established, approved contact route; do not promise a transfer, response time, refund or resolution.
- Leaving a reply held or choosing not to send is a valid operator decision. Social Response Agent does not notify a colleague, complete the business’s outside support process or prove that someone followed up.
Before the first live reply
- Confirm the saved account name is the exact invited Facebook Page. If it is not, stop and use Help instead of continuing with another Page.
- Open Account Health for that Page and follow any recorded attention item. A saved connection by itself does not prove comment collection or publishing.
- Open Brand & Voice and use Try it first with a common question and an edge case. The preview posts nothing; correct the saved facts and boundaries before using a live draft.
- When a captured item appears, compare it with the original Facebook thread, review and edit the draft, then choose whether to send it once. If the recorded result and Facebook thread disagree, do not resend; leave the affected item held and use the support-report guidance.
Practice stop-and-recover decisions before live work
Use the private dry-run card to rehearse the empty, permission, loading, duplicate-action, unsaved-change, retry, uncertainty and closeout decisions that most often require judgment. Use invented content and the fixed sample only; do not practice on a live customer comment.
- Practice an empty inbox without switching Pages, manufacturing a customer comment or assuming complete capture.
- Practice stopping for a missing Page or permission mismatch instead of using another account, Page or shared credential.
- Practice waiting through loading, handling an unsaved-change warning and distinguishing an explicit safe retry from an uncertain result.
- Practice keeping an interrupted send held, checking the matching Facebook thread once and preparing the support report without repeating the action.
- Practice closing a review window with every touched item accounted for and every unresolved item still held.
A completed dry run is preparation, not independent-operation evidence. It does not count toward the seven distinct customer-operated dates or create the exact native-reply receipt.
Run a week-one operating check
This is a working routine for the invited business, not a claim that the pilot is ready or that the business accepted it. Use real customer sessions to find out whether one operator can run the bounded workflow without Ricky operating it for them.
- Plan one completed operating record on each of seven distinct local calendar dates in the customer account timezone. More than one review window on the same date still counts as one date.
- Use the same named operator and assigned Page for every eligible date. A date does not count if Ricky signs in as the operator; chooses or authorizes the Page; enters or edits business facts or reply boundaries; monitors the inbox or chooses an item; or edits, sends, retries or reconciles a reply for the operator. The pilot does not include continuous monitoring, a backup operator or a promised support response time.
- At the start of each window, confirm the exact assigned Page and read Account Health before opening the inbox. Compare a recent Facebook thread with the captured records; a workspace count is not proof that every comment arrived.
- Review one item at a time. Read the original thread, check the draft against current business facts, then send once, save a draft, intentionally skip it or leave it held. Do not use another Page or reconnect to work around an unclear state.
- At the end of the window, use the closeout steps below. Keep any uncertain send held, check the matching Facebook thread once and prepare the support report instead of repeating the action.
Record evidence after each window
- The local calendar date, customer account timezone, approximate start and finish time, assigned Page and one opaque daily evidence reference that contains no business, Page, operator or customer information.
- Eligible Page comments seen on Facebook, captured records reviewed and any apparent capture gap. Keep the comparison period and exclusions visible.
- Drafts edited, replies confirmed on the original Facebook thread, items skipped or held, and any result that remained uncertain.
- Questions that required support, whether the operator could follow the documented next step, and any step that still required founder intervention.
The reusable log records counts, decisions, distinct-date eligibility and unresolved status without asking for comment text, reply text, customer names or account credentials. Completing it stores nothing with Social Response Agent and contacts nobody.
Make the continue-or-pause decision from evidence
- Continue the evaluation only when the named operator can repeat setup and review safely, knows when to stop, and can prepare a complete issue report without sharing credentials or customer details. Do not mark independent use verified until seven eligible records cover seven distinct local calendar dates.
- Pause the affected workflow when Page identity, access, capture or send status is unclear. A smooth demo, generated draft or connected-account screen is not evidence that the live workflow was accepted.
- Do not claim time saved, complete capture, successful delivery or customer acceptance from this checklist. Those claims require executed customer sessions and the recorded evidence above.
Compare the pilot with its original success conditions
Use the private outcome record to separate business-defined goals, executed operating evidence and the business’s stated next decision. It also keeps seven distinct-date records and the canonical native-reply receipt separate. The record stays on the operator’s device unless they choose to share it.
- Before the first live window, let the business define its own conditions for continuing or pausing. Record an observed baseline only when one exists; otherwise write “Not measured” instead of estimating time saved.
- After executed windows, aggregate counts only from review-window logs that use the same stated Facebook comparison periods. Keep missing windows, capture gaps, uncertain results and founder intervention visible.
- Record whether the named operator can repeat the routine without Ricky signing in as the operator, choosing or authorizing the Page, entering or editing business facts or reply boundaries, monitoring the inbox or choosing an item, or editing, sending, retrying or reconciling replies, and whether the current one-business, one-operator, one-Page scope remains sufficient.
- Record the business’s stated continue, pause, end or undecided choice. That statement is useful retention evidence, but it does not authorize access, provider work, an extension, payment, subscription or changed terms.
- Keep the exact native-reply milestone separate. It qualifies only from the canonical customer-authorized receipt bound to the business, assigned Page and operator; a worksheet entry, app status or thread observation cannot create or verify that receipt.
Downloading or completing the record does not contact Social Response Agent, submit data, change access, extend an evaluation, authorize provider work, create a payment or prove customer acceptance.
Recover after an interrupted review
- If the page closes, times out or loses its connection during an action, stop clicking. Do not repeat the action just because its result is not visible.
- Reopen Social Response Agent, select the exact assigned Page and reload the affected screen. If you had only typed a draft and had not selected Save or Send, compare it with the original comment and re-enter it if needed.
- If a business-settings save was interrupted, reopen Brand & Voice and compare the currently saved values before deciding whether to save again.
- If a reply send was interrupted or its status is unknown, check the exact original Facebook thread once. If the reply is visible, do not resend it. If it is not visible or remains unclear, leave the item held and use the prepared support report; do not reconnect to recover a send.
Reloading and comparing recorded state are recovery checks, not proof that Facebook received an action or that every comment was captured.
Close every review session safely
- Return to the assigned Page’s review inbox and account for every item you touched: sent once, saved as a draft, intentionally skipped or left held. Do not resend an item to make its status look complete.
- For any send result that is not clear, open the exact original Facebook thread once. If the reply is visible there, do not send it again. If the two views disagree or you cannot confirm the thread, leave the item held.
- Open Account Health again. Follow only its explicit next step; reconnect only when it reports revoked access or a connection receipt says a new attempt is safe.
- For anything still unresolved, note the Page, screen, approximate time and exact status text, then use the prepared support report. The report link opens your mail app but does not send anything.
This closeout accounts for work recorded in Social Response Agent. It does not prove that every Facebook comment was captured or that Facebook accepted every reply.
What this checklist does not do
Reviewing it or downloading the log does not reserve a place, create an account, connect a Page, start an evaluation or payment, or prove that Facebook permissions and comment delivery work for your Page.
The dry run, before-first-reply, week-one routine, outcome record, interruption-recovery and closeout steps are operator readiness aids. They do not establish provider delivery, customer acceptance, time saved or complete Facebook comment capture. They also do not create a canonical native-reply receipt or prove seven eligible dates.
The first-five scope is one business, one verified user and one eligible Facebook Page in Approval first. Instagram, additional Pages, team access and automatic replies are not included.
Not invited yet?
You can explore the fixed sample inbox without a social connection or payment. Sample actions do not post to Facebook and do not establish pilot acceptance.
