Schedule Proposals

A cross-promotion only runs when both sides have agreed the same go-live date, time, timezone and duration. Schedule proposals are how that agreement is negotiated: one side proposes, the other side decides. You can never rule on your own proposal.

Proposals happen in two situations:

1. Before confirmation — you joined a campaign (or accepted a request whose go-live had passed) and want different timing than the creator set.
2. After confirmation — plans changed, and either side wants to move a campaign that is already locked in.

Both use the same panel and the same rules.

Before you start

• Only a participant of the campaign can propose — the creator or the partner who joined, nobody else.
• The campaign must still be in setup: Awaiting confirmation, New time proposed, or Confirmed. Once it is handed to the delivery queue as Scheduled, the timing is locked.
• Your account needs a reliability score of at least 5.0/10 and no open review, exactly as at create and join.
• The new time you propose must be in the future and within 14 days, with one of the standard durations.

Step by step: proposing new timing

As the joiner, during the join flow

On the join page's final pane, choose Propose changes instead of Keep this schedule. The scheduler opens pre-filled with the creator's timing. Adjust the date, time, timezone or duration and send it. You see "Changes sent ✈️", and your partner is emailed and DM'd.

From the campaign page

On /telegram/dashboard/cross-promotion/campaign/YOUR-CODE:

1. Find the button for the state you are in. On a campaign in Awaiting confirmation, the joiner sees Propose changes next to Accept & confirm. On a Confirmed campaign, either participant sees Propose new time.
2. Press it. The Propose new timing panel opens with the shared scheduler and the line "Your partner will review and approve this new time before it takes effect."
3. Pick the new date, time, timezone and duration.
4. Send it. The campaign moves to New time proposed, and your partner is emailed — plus a Telegram DM if their account is linked.
5. Your side of the page now reads Waiting on your partner: "You proposed new timing. Your partner will review and accept or decline — we'll email you the moment they do."

A confirmed campaign stays reschedulable even after its go-live has passed

The Propose new time button does not disappear when the agreed moment slips by. A confirmed campaign has never reached the delivery queue, so nothing was posted and a new time is always a legitimate ask — and a missed window is exactly the case this feature exists to rescue. Only the new time you propose has to be in the future. Both sides keep the posts they already built and approved; nothing is thrown away.

Reviewing a proposal sent to you

Your campaign page shows the banner New schedule proposed — Your partner proposed new timing. Review the changes and accept or decline. with the two schedules side by side.

Column	Contents
Currently agreed	The schedule as it stands — go-live, timezone, duration, end time
Partner proposes	The new schedule they want

Below the comparison sits an optional Reason if you decline (optional) field (up to 300 characters) and two buttons.

• Accept changes — the new schedule takes effect immediately and the campaign is confirmed. Both of you are emailed the updated details.

• Decline — the campaign reverts to what it was:

  • a previously confirmed campaign stays confirmed on its original time;
  • a never-confirmed campaign drops back to Awaiting confirmation, where the joiner can accept the original schedule or propose again.

  The proposer is notified by DM and email, and your reason — if you gave one — appears on their campaign page as "A proposed reschedule was declined. Reason: …".

Rules

• One decider. Only the side that did not propose can accept or decline. If you proposed, you wait.
• Any number of rounds. A declined or superseded proposal ends nothing; either side can propose again while the campaign is still in setup.
• Everything travels together. Date, time, timezone and duration are all part of one proposal, within the same limits as creation.
• Notifications at every step. Sent, accepted, declined — both sides get email, plus Telegram DMs when linked.
• Posts are untouched. Rescheduling never resets a built post or an approval. Only editing a post does that.

When a time has already passed

Three related cases, and they behave differently:

• Accepting an elapsed go-live is refused. A code can sit for hours before anyone acts on it. If the proposed go-live passed in the meantime, pressing accept returns "That proposed go-live time has already passed — ask your partner to propose a new time." This applies both to the joiner's initial accept and to accepting a partner's proposal.
• Proposing on a confirmed campaign whose go-live has passed is allowed — see the note above. This is the normal way to rescue a campaign that missed its window.
• Accepting a partnership request whose go-live passed creates the campaign in Awaiting confirmation rather than Confirmed, and the requester is told to agree a new time. The proposal flow above is exactly how.

Once delivery starts, timing is locked

Proposals are possible only while the campaign is in setup. Once both posts are approved and the campaign is handed to the delivery bot as Scheduled, the schedule can no longer be changed — your options are to let it run or cancel before go-live.

There is a six-hour grace on a late hand-off

A campaign that only becomes ready after its agreed start — usually because the six-hour review auto-approve landed late — is still published if it becomes ready within 6 hours of the go-live. Past that, the run is deliberately abandoned rather than posted a day late, and the campaign page says so with a "This campaign missed its go-live window" banner. Propose a new time from there.

If something goes wrong

What you see	What it means	What to do
"This campaign can't be changed right now — it may not have a partner yet, or its go-live time has already passed."	No partner has joined, or the campaign has already reached the delivery queue.	Wait for a partner, or — if it is Scheduled — cancel before go-live and start fresh.
"That proposed go-live time has already passed — ask your partner to propose a new time."	The proposal you are accepting has itself elapsed.	Propose a fresh time yourself; you are now the proposer, and they decide.
"You proposed this change — your partner decides on it."	You tried to rule on your own proposal.	Wait, or withdraw by proposing again with different timing.
"There are no pending changes to review."	The proposal was already decided, or withdrawn.	Reload the campaign page for its current state.
"Pick a go-live time in the future." / "Go-live must be within 14 days."	The new time is in the past or outside the window.	Pick a time inside the next two weeks.
The banner "This campaign missed its go-live window"	The campaign became ready more than 6 hours after its start. Nothing was posted in either channel.	Your posts are still saved. Press Propose new time and run it.

From the support chat

Accept the new time my partner proposed or decline it decides a proposal from the chat, after you type CONFIRM. What the assistant can do for you has the full list and the confirmation rule.

Related

• Joining a campaign — where the joiner first chooses between accepting and proposing.
• Creatives: posts and delivery — the step the agreed schedule unlocks.
• Campaign lifecycle — the alternative when the timing cannot be saved.
• Partnership requests — where an elapsed proposed go-live comes from most often.

---

Next: Creatives: posts and delivery — with the schedule agreed, it is time to write the post that runs in your partner's channel.