1. Notify the Right Users When a Form Is Submitted
Use the Notify option in your form’s Post‑Submission Settings to alert specific users or groups. Many teams also create a Request Management dashboard to track all submissions in one place.

2. Automatically Add the Request to Your Content Calendar
Use the Rule Engine (Context: Request) → Trigger: Request Submitted → Action: Convert to Message.
Map your form fields (e.g., request copy → caption) and set the post to Draft so nothing publishes automatically.

3. Add an Approval Workflow Before Publishing
Set up Tiered Approvals in Governance and create an approval path for content originating from your intake form.
Then, in the Rule Engine, route your newly created drafts into this approval path.
Optional: Add an Approval Queue to your dashboard for quick reviewing.

Best Practices

• Make key fields in your form mandatory (Preferred Date, Channel, Copy, etc.).
• Save uploaded files automatically to the DAM.
• Ensure approvers have Publishing rights; requestors should only have Edit access.
• Submit a few test forms to confirm notifications, calendar creation, and approvals all work end‑to‑end.