VYG Docs
Guides for brand teams

Drafting campaigns

Draft and change text campaigns, discounts and message tests with Claude, then review and launch them in VYG.

Claude can do the first draft of a campaign for you: pick what starts it, write the messages, add steps, and attach a discount. You then review it and decide when it goes live.

Claude works with campaigns through two tools:

  • campaigns reads. It lists your campaigns, opens one (its trigger, schedule, holdout, re-entry rule, audience filters and every step), shows run activity, follows one event through every campaign, lists message variants, and says what your brand can build with.
  • manage_campaign changes. op: "create" makes a new paused draft, and op: "create_blast" makes a new scheduled blast as a paused draft. op: "update" applies a list of changes to one campaign.

campaigns has no performance numbers. For results, see Reporting on performance.

New campaigns start paused

Every new campaign is saved paused. Review it, then turn it on in the vyg.ai app or ask Claude to turn it on. Turning a campaign on starts texting real customers, so Claude sends set_status: active only with confirm_activation: true, after you explicitly agree. See Going live safely.

Claude follows the same rules as the VYG app. Any brand can create and change campaigns. Some steps and triggers need a feature, and some steps need an integration connected first, as in the app's add-step menu. See Beta features. You also need to be signed in with your own VYG login (not an API key) for Claude to make changes.

Start by asking what is possible

Every brand has its own triggers, message rules, discounts and step types. Claude reads them with campaigns view: "options":

  • "What can start a campaign for my brand?"
  • "What kinds of steps can you add to my campaigns?"
  • "What discounts do I already have in my library?"
  • "What personalisation can I use in messages, like first name or product name?"

The options list the same triggers and steps the VYG app offers your brand. Each step type says what Claude can do with it and the settings it takes. A step that needs setup first, such as a channel to connect, carries unavailable_reason. While your brand still texts from a temporary number, texting_setup carries the same warning the app shows on text and agent steps. Message variables for a trigger come from the same list the app's message editor uses. See Campaign steps.

Drafting a campaign

A campaign starts when something happens. The starting points available to most brands are:

  • Checkout abandoned: a shopper left without paying.
  • Order placed: a customer completed an order.
  • Subscription changes: a subscription was created, activated, updated, paused, cancelled or expired, or a subscription payment succeeded or failed.
  • Your own events, if your brand has custom integrations set up in VYG.
  • Checkout started, order shipped, customer replied and customer opted out, and your brand's registered customer events (such as returns.requested), when your brand has those triggers turned on.

The list-building trigger (list/subscribed) belongs to a sign-up list's welcome campaign. It is set up from List building, so neither the app nor Claude moves another campaign onto it, and a welcome campaign keeps it.

Describe what you want in plain words. Include:

  • What starts it, from the list above.
  • How long to wait before the first message.
  • How it is handled: an automated text, or a conversation with your LiveRecover agents.
  • Any later steps, such as a wait and a WhatsApp follow-up.
  • Who it is for, if not everyone. Ask Claude which details you can target on for that starting point.
  • The offer, if any.
  • The tone.

Examples:

  • "Draft a campaign for abandoned checkouts. Wait 30 minutes, then send a friendly text reminding them what's in their cart. Offer free shipping. Call it 'Cart reminder, free shipping'."
  • "Draft a campaign that texts customers 3 days after their order to thank them, then a day later sends our order_update WhatsApp template."
  • "Draft a campaign for when a subscription is cancelled. Wait one day, then have an agent reach out to ask why and offer 20% off to stay."

Claude creates the draft and gives you a link to open it in VYG. Review it there before you switch it on.

On abandoned checkout campaigns, the agent's reply must include the link back to the customer's checkout. Claude adds it for you.

Route likely buyers to a conversation

For a brand with the CDP predictions beta, campaigns view: "options" lists the purchase_likelihood and purchase_band audience filters on checkout and order triggers, and Claude can set them with set_filters. Brands with Klaviyo connected also get Klaviyo list and segment filters (klaviyo_lists, klaviyo_segments, by Klaviyo id).

In the VYG app, open an abandoned checkout flow and add a branch with the filter purchase_band is top. Connect the matching branch to a LiveRecover agent step. Leave the default branch on the usual automated checkout sequence. Customers without a score have band unknown and follow the default branch.

Automated outbound steps still pass the A2P and per-channel consent checks.

Changing a campaign

Claude first reads the campaign with campaigns view: "get" to find its step ids, then sends one manage_campaign op: "update" call with a list of changes:

ChangeWhat it does
renameA new name.
set_scheduleStart and end dates. null clears one. See quiet hours below.
set_filtersReplaces who the campaign is for. An empty list removes the filters.
set_holdoutTurns the holdout group on or off, or changes its share (1 to 50%).
set_re_entryWhether a customer can enter once, or again after a period.
set_triggerChanges what starts the campaign, its start delay, or both.
add_nodeAdds a step after another one. After a split, name the branch.
update_nodeChanges a step's settings, or the text of a text or agent step.
remove_nodeRemoves a step.
add_variant, update_variantAlternative wording for a message. Staff only, as in the VYG app.
republishPushes the saved steps to the running campaign again.
set_statusactive turns the campaign on; paused turns it off.

Examples:

  • "Rename my 'Cart reminder' draft to 'Cart reminder, October' and set it to run 1 to 30 November."
  • "Make the first message shorter and more casual."
  • "On the B branch of the split, wait two hours before the text."
  • "Only send it to carts over $50."
  • "Hold back 10% of customers so we can measure the lift."

The changes apply in a fixed order. Pausing (set_status paused) runs first, so nothing sends while the changes land. A trigger change (set_trigger) runs next, with the app's rules: a trigger your brand cannot use is refused, a predefined trigger needs Shopify connected, and moving to one of your own events detaches the campaign's discounts. Checkout started and order shipped have no start delay. All campaign edits (everything except variants and set_status) save together: either all of them are saved, or none are. Then variant changes run one by one. Turning the campaign on (set_status active) runs last, and only if everything before it worked, including updating the running campaign. If a step fails part-way, Claude tells you what was applied, what failed and what was not tried.

If someone saved the campaign in the VYG editor while Claude was preparing a change, nothing is saved and Claude reads the campaign again before retrying.

Messages follow your message rules (for example length and required wording). If a message breaks a rule, Claude will say which one and suggest a fix.

Some steps can only be changed in the VYG app, such as discount steps and branch conditions. A campaign that contains a branch condition, a Klaviyo step or a Slack step can still have its name, dates, filters, holdout and messages changed by Claude, but its steps have to be changed in the app. campaigns view: "get" marks which steps Claude can edit.

Copying a campaign

"Make a copy of my 'Cart reminder' campaign." Claude sends manage_campaign op: "duplicate". The copy is a new paused draft with the same steps, messages, filters and discounts, made the same way as the VYG app's Duplicate action. The original is not changed.

Going live safely

Two confirmation flags protect your customers:

  • confirm_live_change: true is needed for any change to a campaign that is already on, because it reaches customers who are already in it. Claude sends it only after you agree to change a live campaign. You can also pause the campaign first.
  • confirm_activation: true is needed to turn a campaign on (set_status: active), because that starts texting real customers. Claude restates the campaign and sends it only after you explicitly say yes. Pausing needs no confirmation.

Without the flag, the whole request is refused and nothing is changed.

Quiet hours

Texts only go out between 8am and 8pm in each subscriber's local time (12pm to 8pm in Texas, and 7pm to 11pm UTC when VYG does not know their time zone). A text due outside those hours waits for the next allowed time, and nothing sends after a campaign's end time. A short window that starts in the evening can end before some people are reached, so Claude points this out when you set a schedule.

Scheduled blasts

A blast is a one-time text to an audience at a set time. Blasts show in the campaigns list with a blast block: the channel (SMS or Telegram), the audience, the send and stop time, where the blast is in its run, and whether Claude can still change it.

  • "What blasts do I have scheduled?"
  • "Who will my 'Holiday sale' blast go to, and how many people is that?" Claude reads campaigns view: "audience", which also says whether the blast can launch now and, if not, why (for example a segment that has not been counted yet).
  • "How is my 'Holiday sale' blast doing?" Claude reads campaigns view: "delivery": texts queued (with the next send time), sending, sent, delivered, failed, unsubscribed before send and on hold, and how many people were reached.

Texts go out between 8am and 8pm in each subscriber's local time; texts due outside that window wait until 8am. A text the carrier refuses because the brand reached its daily 10DLC limit is queued again shortly after the next midnight Pacific reset, at most twice, and not after the stop time.

Creating a blast

"Create an SMS blast for our Early Black Friday sale to the VIP segment, sending Thursday at 10am Pacific: 'Early access is live. Reply STOP to opt out.'" Claude sends manage_campaign op: "create_blast". It makes the blast the same way as the VYG app's Scheduled (Blast) campaign type: a paused draft named "Blast N" unless you give a name, sent to all subscribers unless you pick a segment, sign-up form or subscriber import, with one SMS step and no send time. The message, audience, send time (starts_at) and optional stop time (ends_at) can be set in the same request, under the same rules as changing a blast. Creating a blast sends nothing; turning it on is the separate launch step below.

Creating a blast needs blasts on your account and a connected, enabled Infobip integration, as in the VYG app. While blasts are in shadow mode for a brand, ask your VYG contact to create them.

Changing a blast

Claude can change what the VYG blast editor changes, while the blast is a paused draft:

  • its name, send time and stop time (set_schedule: starts_at is the send time, ends_at the stop time),
  • its audience (set_audience): all subscribers, a segment, a sign-up form or a subscriber import. The audience is checked the same way as in the VYG app before it is saved,
  • the text of its message.

Its steps, filters and holdout are changed in the VYG app. A blast that is turned on has to be turned off first: one that has not started sending goes back to Draft and nothing is sent. Once a blast has started sending it can no longer be changed, only paused or resumed; duplicate it in the VYG app to run a changed version.

Launching a blast

Launching a blast texts everyone in its audience

Turning a blast on (set_status: active) texts every subscribed person in its audience at the send time. Claude restates the audience, the send time and the message, and sends confirm_activation: true only after you explicitly agree.

Launching runs the same checks as the VYG app: your plan allows turning campaigns on, your account has blasts, there is a send time (or send_now: true, the app's Send now), the stop time, if you set one, is after the send time, the blast has a message and no live agent step, the channel is connected, and the audience can be sent to. A saved send time that has already passed sends right away. Pausing a blast that has started sending keeps the texts already sent and holds the rest. Turning it back on lets the held texts go out, adds nobody new, and keeps the original send time; once its stop time has passed it cannot be turned back on, so duplicate it to send again. Pausing and turning on are separate requests.

Discounts

Claude can add a discount to your discount library, or change one that is there.

  • "Create a 15% off discount that lasts 7 days, with codes starting WINBACK."
  • "Create a free shipping discount for orders over $50."
  • "Change my WINBACK discount to 20% off."

Discount types are percentage off, a fixed amount off, or free shipping. You can add a minimum order amount or minimum number of items, how many days the code lasts (up to a year), and a code prefix.

Discounts take effect straight away

A new or changed discount is saved to your library and your Shopify store immediately (Shopify stores only for now). Changes apply to codes created from then on. Double-check the amount before you ask.

A minimum spend belongs on the discount, not on who the campaign is sent to.

Testing different messages

You can try alternative wording for a campaign message and see which works better. Each alternative is called a variant. Adding the first alternative starts a test with the existing message as its control. Reading variants needs beta:flow-builder-variants (staff accounts can always read them). Adding or changing variants is staff-only, as in the VYG app.

Variants can be added or edited on active campaigns. Changes can affect subsequent messages, including when you edit the control. Review the proposed wording and confirm the target campaign before applying changes.

  • "Show me the message variants on my 'Cart reminder' campaign."
  • "Add a variant to the first message that leads with the discount instead of the product."
  • "Update variant B to mention free returns."

Checking what a campaign did

  • "What does my 'Cart reminder' campaign do, step by step?"
  • "Who entered my 'Cart reminder' campaign yesterday, and who was skipped and why?"
  • "Did order 1042 go through any campaign?"

For results such as recovered sales, see Reporting on performance.

Which campaigns Claude can see

Claude lists and opens the same campaigns the VYG app shows you:

  • Legacy (v1) workflows are listed next to your campaigns unless your brand has moved to the Campaigns builder. After the move they are hidden and read as not found, unless the legacy workflows setting is turned back on for your brand. They are always read-only here.
  • Scheduled blasts in shadow mode are left out of the list, comparisons, campaign performance, run history, delivery and audience, and cannot be opened or changed.
  • A trigger named like namespace.event is offered only when your brand has an enabled registration for that event. See Beta features.

On this page