> For the complete documentation index, see [llms.txt](https://docs.slapfive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slapfive.com/getting-started/slapfive-best-practices/slapfive-self-guide-enablement/workstreams-and-workflow-automations/request-management.md).

# Request Management

Requests are the operational engine of SlapFive. A request represents a customer advocacy action.

 **Examples include:**\
• Reference calls\
• Customer quotes\
• Reviews\
• Surveys\
• Referrals\
• Speaking opportunities\
• Case study participation\
\
**Request Lifecycle -** A standard request usually follows this process:\
1\. Request creation\
2\. Internal review or approval\
3\. Advocate matching\
4\. Outreach and coordination\
5\. Fulfillment\
6\. Reporting and tracking\
\
**Manual vs Automated Matching**\
Some organizations manually select advocates, while others automate matching based on profile data and segmentation rules.\
\
**Visibility Across Teams**\
Sales, marketing, customer success, and advocacy teams may all interact with requests differently. Proper visibility settings ensure teams can collaborate efficiently while protecting customer data.\
\
**Best Practices**\
• Create clear request descriptions\
• Define approval ownership\
• Set realistic timelines\
• Track fulfillment outcomes\
• Monitor request completion rates

{% embed url="<https://drive.google.com/file/d/1ju-xcN1OiNw20SZkSIpHlTHl1-Z4RV7n/view?usp=sharing>" %}