← Help center

Review Consultant proposals

How proposals work

The Consultant prepares proposed changes for an owner or admin to review. A proposal does not change your account when it is created.

Consultant usage draws down your credits, including usage that analyzes your account and prepares a proposal. The proposal remains review-only until an owner or admin approves it.

Before it files a proposal, the Consultant works out the exact before-and-after each change would produce and reviews that itself. It cannot file a proposal it has not worked through this way, and if it changes its mind about any part of the proposal it has to work the whole thing through again. This is a check on the Consultant, not on you — your approval card and your decision are unchanged.

The Consultant prepares one proposal at a time and waits for your decision before preparing another. If you want it to work on something else in the meantime, ask it to wait on the earlier proposal or decide on that one first.

A proposal can bundle several related changes into one card — for example, adding a new column to your customer table and showing it in your layout. You approve or reject the whole bundle together; there is no way to approve part of it.

A proposed column can be one your team fills in by hand, as well as one filled in automatically from a report. If a column with the same name already exists, the card says so under Be aware — approving adds a second one rather than replacing the first.

When a proposal edits a report and the edit no longer lists a field that report used to produce, the card names the dropped fields under Be aware. Any customer-table column filled in from one of those fields stops being filled in once the change is approved, so check whether a column depends on a field before approving its removal.

Each approval card shows:

Phase bundles also show an affected-flow summary when the proposal itself names the affected Phases and paths. It marks added and removed items. A proposal does not guess at Phase paths that were not included in its review data.

Most proposals list no warnings and no assumptions. Each section appears only when there is something that could change your decision.

The Consultant can also propose creating, editing, or deleting an automated customer-workflow routine. These cards show the routine's allowed actions and limits before its wording, so you can review what it can do as well as what it says.

A routine deletion card lists the senders where the routine is enabled and the number of conversations currently using it. Those conversations return to the normal customer flow after deletion.

Proposals prepared during an account audit are marked Proposed during your account audit.

Only an owner or admin can approve or reject a proposal.

A proposal that changes how your account behaves right away, or that reaches your customers directly, carries an extra banner asking you to review it carefully before approving. A proposal that would message customers always shows the exact recipient count and message content on the card — Yapper never lets you approve that kind of change without seeing exactly who receives it and what it says.

Approve a proposal

When the Consultant prepares a proposal, it posts a Review proposal button on that message in your support chat. Select it to open the proposal for review: read What will happen, the rationale, and each labeled change, and expand Show technical details when you want the complete before-and-after comparison. Then select Make these changes. For a bundle, this applies every change in it. Yapper asks you to confirm before applying a bundle or a proposal with an item to review carefully. Once the proposal is decided or can no longer be decided, the button names its current outcome and offers View details instead.

Approval checks the current account settings again before applying the change, and re-checks that your billing is current. If your subscription is not active, Yapper refuses to apply the change and points you to billing. The proposal is not used up — it stays pending, and you can approve it once your account is current. Playbook and Phase changes are recorded in Playbook history. Handbook changes preserve entries written by you and identify Consultant-added products separately.

After approval, the card says Being applied while Yapper completes the changes. You can close it and return later; opening it again refreshes the outcome automatically. The decision buttons stay unavailable once approval is accepted.

Playbook history records the outcome of a proposal whether or not it changed anything. An applied proposal appears as a new version you can compare and roll back. A proposal you rejected, one that could not be completed, one that was only partly applied, and one discarded because its consulting session ended each appear there too, with the reason it settled that way. So a proposal never simply disappears: you can check what became of it without asking.

A Schedule proposal is configuration for future customer messages. Review its timing, recipient filter, sender, message type, and recipient count carefully before approval. Recipients are resolved again when a Schedule runs, so the future audience can differ from the count on the approval card.

Reject or replace a proposal

Select Don't make these changes when you do not want the change. You can include an optional reason before confirming. Rejection does not modify the account.

Your decision goes straight back to the Consultant in the conversation the proposal came from, whether or not you gave a reason, so you do not have to explain it yourself. The Consultant acknowledges the decision rather than arguing for the change or proposing the same thing again; it may ask what you would prefer instead. A reason you do give is kept with the proposal, so a later consulting session can refer to it if you ask for the same change again.

If the related Playbook, Phase, Handbook, Schedule, or customer-workflow routine changes after the proposal is prepared, Yapper does not overwrite the newer work. The proposal is marked stale instead — for a bundle, this happens if any one of its changes is affected, even if the others are still current.

Approval always re-checks the proposal against your account's current setup one more time, right before applying it. If something material changed since you first saw the card — a different setting, a different target, or a different customer-facing effect — Yapper does not apply it. Instead it marks that proposal stale and automatically prepares a fresh one reflecting the current setup, which the Consultant posts to your support chat with its own Review proposal button. Approving the fresh proposal is a separate step; nothing is applied until you do.

For any other stale proposal, ask the Consultant to review the latest setup and prepare a new proposal.

If an approved bundle stops after some changes were applied, its status is Partially applied, even when the stopping point is found on a later attempt. Review which changes landed before asking the Consultant for another proposal. Stale and Failed mean no change in that proposal was recorded as applied.

Ending a session with a proposal pending

A proposal you have not yet approved, rejected, or asked to change belongs to the consulting session that prepared it. Ending that session — by selecting End, or by letting the session sit idle long enough that it closes on its own — discards any proposal still waiting on your decision; nothing from it is applied. If a pending proposal is why you have not ended the session, selecting End asks you to confirm first, since ending discards it. A proposal you have already approved, rejected, or that has already been applied is unaffected — only one you have not decided on is discarded when the session ends.

Ask for a change to a proposal

When a proposal is close but not quite right — the wording of a reminder, a number, a target — you do not have to reject it and start over. Select Ask for a change, describe what you want adjusted in your own words, and confirm.

The proposal you commented on stops being approvable straight away, while a revised version is being prepared. The Consultant reads your comment and replies in the same conversation with a revised proposal, which you open and decide the same way. Approving it is a separate step; nothing is applied until you do.

You can have one comment outstanding per proposal at a time. While a revised version is being prepared, the original cannot be commented on again — if you change your mind about the direction entirely, reject it instead and ask the Consultant for a new proposal.

Your comment is kept with the proposal, so the Consultant can see what you asked for and why the revised version differs. A comment is not a rejection: it tells the Consultant the change was right in kind but wrong in degree, which is a different signal from turning it down.

If a revised proposal cannot be prepared, the Consultant lets you know in the chat and asks you to try again. Comment on the original once more to ask for another attempt.

When a change does not apply

Approving a proposal can still fail — a setting it depends on may have moved, or a change may be refused at the moment it is made. When that happens the card shows the failure and your account is left as it was.

You do not have to report the failure yourself. It goes back to the Consultant in the conversation the proposal came from, with the reason and which parts of the change were reached, and the Consultant works out what went wrong and prepares a corrected proposal for you to review. Approving that one is a separate step, as always.

When part of a change was applied

Most changes either apply completely or not at all. A small number cannot be taken back once they start — sending a Schedule to a live audience, for example. If one of those succeeds and a later change in the same bundle then fails, the proposal is marked Partly applied and its card says so directly: some of the changes were made, could not be undone, and your account may be partly changed.

The Consultant is told about this case too, but it deliberately does not prepare a replacement on its own. Because your account has been left part-way through a change, it explains what was made and what was not, and waits for you before proposing anything further. Review the affected settings alongside that explanation, so the next proposal is prepared against what your account looks like now rather than repeating work that already landed.

Follow proposal outcomes

Playbook history is where a proposal's outcome lands once it is settled (see playbooks). An applied Playbook or Phase change appears there as a version you can compare and roll back. A rejected, failed, partly applied, or discarded proposal appears there too, with the reason it settled that way. Opening one shows the same labeled before-and-after changes you saw when reviewing it, so you can see exactly what was proposed; for a partly applied proposal, the changes shown are the ones that were actually made. So a proposal never simply disappears: you can check what became of it without asking, and there is no separate list of pending proposals to browse. The button on the chat message that announced the proposal says Review proposal while a decision is available, then names the outcome and opens its details after it settles.