Approve or decline a content request
Decide on a new content request, see what the creator decided in their portal, and what happens after.
What it's for
A new content request stays Submitted until someone decides. As a Manager you can approve it (the creator will make it) or decline it (with a reason). If the creator has a login for the creator portal, they can approve or decline it too. Whoever decides first wins.
Before you start
- You're signed in as a Manager.
- There is a TEST request with the status Submitted: the test Chatter sends one with a fan username that starts with TEST (see the Chatter guide). A request you send yourself doesn't work here: you can't decide your own requests. Never decide a real request while testing.
- To test the creator's side, the request must be for a test creator account linked to the Creator test account (an administrator sets this up; the owner shares the test accounts privately). Never use a real creator for this: they see the request in their portal.
Steps
Open a request waiting for a decision
Click Operations → Requests. The Needs review tab lists the Submitted requests. Click one.
Check whether the creator can still decide
Under what the fan asked for:
- "Waiting for the creator's decision. They see this request in their portal and can approve or decline it." means the creator has a portal login and hasn't decided yet.
- Nothing is shown when the creator has no portal login. Only the agency decides.
For a Custom video, a yellow warning above what the fan asked for means the tip doesn't match the model's price on the Model sheet: the tip is below the model's custom video minimum, the model doesn't offer custom videos, they need approval, or the model has no custom video price. It is only a warning; you still decide.
Approve the request
In the Approve or decline box ("The submitter sees your decision and note."), you can add a Note. Click Approve.
Or deny it
Write the reason in Note (it is required when declining, at least 3 characters). Click Decline.
See what the creator decided
When the creator decides first, the request page shows a box Creator approved or Creator declined, with their name, the time and, for a decline, their reason. The status is already Approved or Declined, and the Approve or decline box is gone.
What you should see
- Approve: the message Request approved., the status Approved, and in History "Accepted." (or "Accepted:" followed by your note).
- Decline: the message Request declined., the status Declined, and in History "Declined:" followed by your note.
- The request leaves the Needs review tab. The chatter sees the new status and your note in their own list.
- A creator's decision: in History, "Creator approved." or "Creator declined:" followed by their reason, under the creator's name.
Test checklist
Good to know
If two people decide at nearly the same time, the second one sees "This request was already approved.", "Declined requests are final." or "Someone updated this request. Reload and try again." Reload the page to see the decision that won.
After you approve
Approving does not move the request further. An administrator moves it to In progress and Ready and records the payment. Whoever sends it to the fan marks it Sent (Mark a custom sent). If a declined request should be decided again, ask an administrator to reopen it.
Nobody is emailed about decisions yet: tell the chatter, or let them check the request's History.
Your own requests
The Approve or decline box doesn't show on a request you sent yourself: another manager or an administrator decides it. Staff requests work the same way.
You are testing on real data
The test app shares its data with the live app, and a content request can't be deleted. Only work on TEST requests: ones you or the test Chatter sent with a fan username that starts with TEST. Never accept, deny or assign a real request while testing. When you're done, deny the test Chatter's open TEST requests with the note "TEST – done". Ask an administrator to deny or cancel your own.