# linkedin-boost (Agent Skill)

> A runbook for boosting one LinkedIn Company Page post that promotes a blog post: a budget sized to the run, the image, post and first comment, founder reposts, a named person on every task, and dates that move together.

Page: https://timerise.ai/skills/linkedin-boost

Agent Skill `linkedin-boost`: https://github.com/timerise-ai/linkedin-boost. Category: Marketing. Runs on Next.js; backend: No data store, markdown posts in the repository; people, conversion vocabulary and languages behind a seam.

Latest release: v0.1.3 (2026-10-07).

Install: npx skills add timerise-ai/linkedin-boost. A tool for an agent, not a module: nothing for Timerise to build or quote.

Boosting a Company Page post is the cheapest paid test on LinkedIn, and the easiest to waste. The post carries no link, so LinkedIn cannot optimise for visits to the site. Every sign-up depends on readers opening the first comment. The Boost button also hides most of the settings that decide where the money goes.

What makes a boost work happens around it: the image, the first comment with the link, the first 90 minutes, founders reposting with their own words, messages to the people who know you. When nobody's name is on those tasks, they do not happen, and when the publish date moves, half of them stay on the old day.

This skill gives an agent the runbook we write for every boost: what the boost can and cannot buy, a lifetime budget sized to the run, the post, comment and image traced to the blog post, the Campaign Manager build with every setting visible, a named person on every task, weekly decision rules, and one date that moves everything else with it.

Write a runbook for boosting one LinkedIn Company Page post that promotes a blog post: what a boost buys and what it cannot, a lifetime budget sized to the run, the image, post text and first comment with the link, the first 90 minutes, founder reposts and network DMs, the Campaign Manager build of an Engagement campaign around an existing post, a pre-launch checklist where every item has a named person, weekly decision rules, and the month-end results row. Use when: (1) a Company Page post with the link in the first comment should get paid reach, (2) a post campaign runbook exists and a boost is the cheaper first test, (3) the publish date moves and the boost, reposts and DMs must move with it, (4) the user mentions: boost, boost this post, boosted post, sponsor the company page post, engagement campaign, link in the first comment, founder repost, repost with your thoughts, DM to our network, BOOST-01, utm_content=boost-01, "who owns this task", "move the post to tomorrow". Carries the trade-off against a Website visits campaign, the build steps the Boost button hides, the date cascade, and the rule that no task is left without a person. Takes the path to the blog post's markdown file as a required argument and stops without it. Written for a Next.js App Router marketing site whose posts are markdown in the repository; the host's people, conversion vocabulary, languages and runbook folder are the seam. LinkedIn only. Not the Website visits campaign (ad-campaign-runbook), not a personal-profile post writer, not an ads API client.

This skill was written by the engineer who has shipped this work. The earlier implementation it was audited against was a boost runbook for a B2B marketing site, written as a delta of a Website visits runbook. The procedure holds the properties a boost runbook has to hold: a lifetime budget whose run days and pace match the dates, every sentence of the post, comment, reposts and DMs traceable to the blog post, a named person on every task and checklist item, a boost built in Campaign Manager with every setting visible, an ad account that is never changed without a yes, and a finished file with no placeholder and no stale date. [`references/provenance.md`](references/provenance.md) has the record.

What it builds:
- What a boost buys and what it cannot
- A lifetime budget sized to the run
- The image
- Post text and first comment with the link
- Founder reposts and network DMs
- The Campaign Manager build the Boost button hides
- A named person on every task
- Weekly decision rules and a date cascade when the publish date moves

When to use:
- A blog post already has, or will get, a Company Page post with the link in the first comment.
- The budget is small and the team wants to learn what the audience engages with before paying for clicks.
- A boost runbook exists and its dates or owners must change.

When not to use:
- **A Website visits campaign with link ads to the post**: the sibling [`ad-campaign-runbook`](https://github.com/timerise-ai/ad-campaign-runbook), whose main runbook this one is a delta of. Never both in one month on one campaign group cap.
- **A post on a personal profile**: the author's own posting skill (a voice skill, if installed). This skill drafts repost texts and hands them to the author.
- **Thought Leader Ads, Meta, Google or X**: not covered, see [provenance.md](references/provenance.md).
- **Creating the campaign through an ads API**: this writes a document a person executes.

Non-negotiables:
- Never run without the post file. Which content gets the budget is the user's decision. A missing, non-file, non-markdown or short post stops the skill, and it asks.
- Never write a claim the post does not make. The company post, comment, reposts and DMs each name the blog post sentence they come from, and the post's caveats bind them. The creative audit drops what has no source.
- Never invent a budget, a benchmark or a fact about a person. Budgets come from the user, planning numbers are labelled as assumptions, a person the user did not name stays a role, and repost texts in someone's voice need that person's yes.
- Never leave a task without a named person. A team is not an owner. The unassigned-tasks pass gets a name for every task or deletes it; when the agent cannot ask, the task stays `open` in the runbook and the handover asks for it, never a guess.
- Never change the ad account without an explicit yes for that action. Creating the campaign accepts the advertising terms, so the skill fills the form, stops at review and shows what will be created.
- Never leave a placeholder or a stale date. One moved date runs the cascade, recomputes the run days and the pace, and the handover greps for `{{` and the old dates.

Not this:
- A Website visits campaign with link ads: The sibling skill [`ad-campaign-runbook`](https://github.com/timerise-ai/ad-campaign-runbook)
- A post on a personal profile: The author's own posting or voice skill. This skill drafts repost texts and hands them over
- Thought Leader Ads, Meta, Google or X: Not covered
- Creating campaigns through an ads API: This skill produces a document for a person to execute in Campaign Manager

What to tell your agent:
- Save the post below as content/blog/en/stop-confirming-bookings-by-phone.md, then write the runbook for boosting our Company Page post about it. 1,500 EUR for November, we post on Tuesday 2026-11-03 at 7:30. Ana publishes and builds the boost, Ben checks tracking, and our two founders repost in Polish. There is no main ads runbook yet.

---
title: Stop confirming bookings by phone
date: 2026-09-01
author: Head of Product
---

Most small clinics and studios still confirm every appointment by phone the day before. A receptionist works down a list, leaves voicemails, and marks the ones who answered. It feels like care. It is mostly lost time. [Try automatic confirmations free for 14 days](/signup).

## Where the first hour goes

We looked at how front desks using our booking software spend the first hour of the day. The confirmation calls were the largest single block, larger than check-ins and larger than rescheduling. The calls also reached the fewest people: a client who books online rarely answers an unknown number at work.

## What we changed

So we replaced the call with a message the client can answer in one tap. Two days before the visit they get a text and an email with three buttons: keep, move, or cancel. Keep does nothing. Move opens the calendar at the same service and the same staff member. Cancel frees the slot at once, and the waiting list gets the offer within a minute.

Three things changed for the clinics that switched. The front desk got its first hour back. Cancellations arrived two days out instead of at the door, which is early enough to fill the slot. And the clients who never answered calls started answering, because a button is easier than a conversation.

## What it does not fix

A client who has decided not to come will not tell you, whatever the channel. A deposit or a cancellation fee is the tool for that, and we do not think a reminder should pretend otherwise. If most of your no-shows come from new clients booking free first visits, start there.

Setting it up takes about ten minutes. You choose when the message goes out, write the text in your own words, and decide whether a cancellation opens the slot to the waiting list or to everyone. Nothing changes for clients who prefer to call: the phone still works, it just stops being the only way.

If your desk still starts the day with a call list, try it for two weeks and compare the first hours. [Start the free trial](/signup).
- Write a boost runbook for our latest blog post, 1,000 EUR this month.
- Save the runbook below as docs/runbooks/linkedin-boost-phone-confirmations.md. We moved the Company Page post from Wednesday to Thursday, same time. Update the runbook.

# Runbook: LinkedIn Boost Post for "Stop confirming bookings by phone"

**Type:** Short campaign runbook (one boosted Company Page post)
**Budget:** 1,500 EUR for November 2026, lifetime, ends 2026-11-30
**Source content:** `content/blog/en/stop-confirming-bookings-by-phone.md`
**Owner:** Ana (post, comment, first 90 minutes, build); Ben (tracking, weekly check, results)
**Status:** Draft, not launched
**Last updated:** 2026-10-20

## 2. Budget and schedule

| Date | What | Who |
| :-- | :-- | :-- |
| Mon 2026-11-02 | Image, post text and comment ready; blog post review | Ana |
| Wed 2026-11-04, 7:30 | Company Page post, first comment with the link | Ana |
| Thu 2026-11-05 | Boost starts (build step 6 start date); first founder repost; DMs start | Ana, Marek |
| Mon 2026-11-09 | Second founder repost | Ola |
| Mon 2026-11-16, 11-23, 11-30 | Weekly check | Ben |
| Mon 2026-11-30 | Boost ends 23:59; results row | Ben |

26 days at 1,500 EUR is about **58 EUR a day**, about 404 EUR a week. Use a **lifetime** budget.

## 4. Setting up the boost

**Owner: Ana.** Step 6: lifetime 1,500 EUR from 2026-11-05 to 2026-11-30 23:59.

## 6. Weekly check (Mondays, 15 minutes)

**Owner: Ben.** Spend under 60% of pace (about 404 EUR a week): raise the bid to the middle of the suggested range.

Agent eval results (newest per agent and prompt):
- Gemini CLI (gemini-3.8-flash) on v0.1.3, 2026-10-07: pass (No data store)
- Codex CLI (gpt-6.1-sol) on v0.1.3, 2026-10-07: pass (No data store)
- Claude Code (claude-opus-5-5) on v0.1.2, 2026-10-07: pass (No data store)

Recent releases:
- v0.1.3 (2026-10-07): Fix release, from scoring the prompt-1 agent eval runs against 0.1.2.
- v0.1.2 (2026-10-07): Fix release, from scoring the prompt-1 agent eval runs against 0.1.1.
- v0.1.1 (2026-10-07): Fix release, from scoring the prompt-1 agent eval runs against 0.1.0.
