Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this for one campaign or ad group at a time.
Read the landing page, the offer, and what the audience is searching for or scrolling past. Choose two to four ideas to test, such as price, speed, a named pain, or proof. Each variant tests one idea, so a result can be read. Note which ideas have run before and what happened.
For each variant give the idea, the headlines, descriptions or primary text, and the call to action. Keep within the platform's character limits and show the count. Match the words on the landing page so the promise carries through. Use the customer's language, not internal product names.
For every claim list its source: the product page, a published price, a review with a link, or the owner's confirmation. Strike any claim with no source, including ratings, rankings, and results. Flag wording an ad platform is likely to reject, such as health, finance, or personal attributes, and anything about a competitor.
Do not upload, launch, or edit ads yourself; draft for approval. Never invent a testimonial, rating, statistic, or result, and never promise a return.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
The English summary is being prepared. Showing the original description.