Audit a copied client campaign’s form and lead routing with AI
Compare the copied form and current integration records with the client’s approved field list and intended destination. Keep old required fields, hidden attribution values and unverified routing visible in the worksheet. Ask the assistant for a proposed field-by-field correction and an owner for each hold. Have an authorized operator check the actual form and the resulting test record before accepting real submissions.
Review the copied configuration as a new campaign
Sociamonials documents copying a campaign from its Actions menu. Its guide says the copy retains configuration and design and starts with an empty submission list. Before promoting the new campaign, check the saved copy against the current brief. Inspect the copied form and its integration separately. An empty entry list tells you nothing about which destination is configured.[1]
Use an AI assistant to compare redacted settings against the approved brief. Give it field names, types, required flags, default behavior and destination labels. Keep credentials, webhook URLs and participant records out of the prompt. The deliverable is a proposed configuration and verification plan, ready for the client and operator to review.
Supply the approved form and the copied snapshot
A fictional agency is preparing a repeat photo contest for Mica Print Shop in workspace MP. Mica’s approved form requires Email for contest contact, permits First name as optional and asks for a required Paper finish drop-down with exactly Matte and Gloss. There is no approved default for those choices. A hidden source field should carry spring_social when supplied by the approved campaign link and stay blank when absent. Phone is outside the brief. The intended destination is the logical queue MP Photo Entries. This brief describes a data handoff for the contest. It gives no authority to add entrants to a marketing list.
The six-row worksheet is the complete supplied snapshot for this check. It describes form fields and the visible integration selection, with the receiving queue unknown. Mica’s original campaign, actual account and records are outside the exercise. Treat the supplied names as planning labels. Verify the real field identifiers and the receiver before relying on a mapping.
Propose the exact field changes
The native form guide documents field types, required and default settings, hidden fields that can collect link parameters, and a preview before saving. F1 and F2 match the brief as supplied. F3 needs a required drop-down with Matte and Gloss and an empty initial selection. Leave a hold if the operator cannot configure and verify that behavior. Remove Phone from the proposed form and from the proposed downstream mapping. Do not edit an existing contact or delete a historical field or value.[2]
F5 contains an old hidden default, autumn_partner. Propose a blank default and verify both approved link cases. In the first case the submitted source should be spring_social. In the second it should be blank; an old campaign value would make the test fail. Inspect the preview and receiver. A hidden field’s value may be absent from the form preview, so read it in the received test record as well.
Verify the destination with a controlled test
Sociamonials’ Zapier guide documents List Integration in the campaign’s Settings step, a test submission and checking the captured fields before mapping the destination step. R1 only supplies the selected integration type. It does not identify the downstream queue or establish that any specific mapping was copied. Ask the integration owner to confirm the exact authorized receiver and its mapping.[3]
After the owner approves an isolated test campaign and test receiver, prepare two synthetic records. T1 uses a tester-controlled address, first name Test, Matte and the approved link that supplies spring_social. Expect the test receiver to show that address, Test, Matte and spring_social. T2 uses a second tester-controlled address, blank first name, Gloss and a link without a source value. Expect that second address, blank name, Gloss and blank source. Neither record includes Phone. Use an approved synthetic image if the test form requires a photo. Keep email and follow-up actions disconnected during this routing check. Test those actions separately with tester-controlled recipients if the owner needs to verify them. The expected values describe this fixture, and the test owner must check how blank fields are encoded in the actual receiver.
Compare both records against the approved form and exact receiver. Check that each arrives in the isolated test receiver only, with the intended client and no unintended follow-up. If routing remains unknown or a stale value appears, keep the launch handoff open until the owner checks the corrected setup. The worksheet proposes two unchanged fields, three field corrections and one integration hold.
Turn the review into a repeatable agency handoff
Reusable prompt: Compare the six supplied settings with the approved Mica form and destination brief. Preserve the observed field type, required flag, options, default and routing state. Return one row per ID with the desired state, change or hold, reason and verification owner. Keep the receiving queue unknown until checked. Return the exact expected values for both synthetic tests, including blank first name and source in T2 and no Phone in either. Keep follow-up disconnected and use an approved synthetic image if the form requires a photo. Do not open accounts, connect a service, change a form or mapping, submit entries, contact anyone or deploy a campaign.
AgencyPro’s API page describes operating across assigned client workspaces. An agency can use the same handoff format in each workspace and keep the settings, test receiver and reviewer tied to that client. The form and Zapier steps above are documented native setup steps. Verify which forms, integrations and agency workspaces are appropriate for your own service.[4]
Illustrative copied campaign settings and proposed corrections
| ID and item | Supplied copied state | Approved state | Reference decision | Owner and verification |
|---|---|---|---|---|
| F1 / Email | Email field; required; no default. | Required for contest contact; no default. | Keep as supplied. | Operator checks preview and compares the test address with the received field. |
| F2 / First name | Text field; optional; no default. | Optional; no default. | Keep as supplied. | Operator checks that T2 can omit it and reads the resulting receiver value. |
| F3 / Paper finish | Text field; optional; no default. | Required drop-down; Matte or Gloss; no default selection. | Propose new type, options and required state. | Form owner checks both choices, no automatic selection and required behavior in the actual form. |
| F4 / Phone | Text field; required; no default. | Omit from the new form and its mapping. | Propose omitting it from this campaign. | Operator verifies absent field and no Phone value handed to the receiver. |
| F5 / Source | Hidden field; old default autumn_partner; link behavior unknown. | Hidden; spring_social when supplied by approved link; otherwise blank. | Propose blank default and verify link input. | Operator checks received T1 and T2 values and keeps the hold if blank behavior is unresolved. |
| R1 / Integration | Zapier selected in List Integration; downstream receiver and field mapping unknown. | Verified MP Photo Entries queue for real submissions; isolated approved test receiver for synthetic records. | Hold actual routing. No queue inferred from the integration name. | Integration owner verifies intended production mapping separately and checks both controlled records in the test receiver. |
When this approach needs adjusting
- The brief, values, labels, proposed changes and test expectations are fictional Codex-authored teaching material. No account, form, link, queue or record was changed or tested.
- The proposed setup may require different actual field identifiers or blank-value handling. Confirm the saved form, original versus copy, and exact authorized receiver before launch.
- This article establishes no automatic import through the AgencyPro API or MCP, consent for marketing, validated delivery or sales outcome.
Return to this next week
Pick one repeat campaign. Run the form and destination review against its new brief. Document the exact configuration your operator verified and note any unexpected field or routing behavior before promoting it.
See how AgencyPro fits your agency