Start free

Approvals

One yes is enough

Your team in the app or the client in their portal: the first yes schedules the piece.

Start freeBook a demo

How a piece gets its yes

  1. Approval is switched on or off client by client, according to what you agreed with each one. With it off, the piece is scheduled straight away.

  2. The piece waits for one approval: a colleague from the app, or the client from their portal, where they see it the way it is going to be published. Whichever comes first counts.

  3. The piece moves to Scheduled and enters the calendar. If someone asks for changes, it goes back to whoever wrote it with the reason in front of them.

What you get

One yes, from either side

There is no order and it is never both: the client does not wait for your team, and your team does not wait for the client.

  • A reminder before the date

    GoFeed writes to the client three days out and again the day before, so the piece does not lose its slot.

  • A history on every piece

    Every approval, every rejection and every request for changes is written on the post, with its date and its author.

  • Asking for changes says why

    The client writes what they want changed and that text travels with the piece. Nobody has to go looking for it in an email.

  • Rejected is a status, not a deletion

    A rejected piece keeps its reason in plain sight and can be brought back. Nothing leaves the queue in silence.

Who it is for

Agencies

Creators

with Creator Studio

Companies

with Creator Studio

Keep going

Put a piece
up for approval

Write a post, send it for approval and watch it reach the calendar with its yes on it.

Start freeBook a demo