Skip to content
GullySales

Call-to-action and microcopy writing · Marketing

A button that says Submit tells the buyer nothing about what happens next.

A buyer is about to ask for a quotation. The button says Submit, the form asks for a reference number the buyer does not have, and the error says Invalid input. Nothing here is a design failure or a build failure. The words are missing, so the buyer stops.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

A writer drafts copy beside printed layouts and a laptop

In one paragraph

Call-to-action and microcopy writing is the writing of the small words a visitor acts on: button labels, form field labels, hints, error messages, confirmation messages and empty-screen text. GullySales reads each journey with you, writes the wording for every step, and hands you a copy sheet that your designer or developer can enter without guessing.

Call-to-action copy is the wording on the things a visitor presses: the button, the banner line, the closing prompt on a page. Microcopy is the wording around them: labels, hints, errors, confirmations. Both are read at the moment of doing, so each word has to say what happens.

This service delivers the words only, on a copy sheet. Screen layout, interface design, form building, tracking and testing are separate scopes. Where a partner scope is needed, such as landing page copywriting for the full page, it can be scoped beside this one.

Who it is for

This is written for you if these sound familiar.

  • A software firm whose sign-up and trial screens use labels written by the developer who built them
  • A manufacturer whose quotation form loses buyers at the field asking for details they do not have
  • A restaurant or hotel whose booking confirmation leaves guests unsure whether the booking is made
  • A clinic whose appointment form produces error messages that patients cannot act on
  • A shop whose basket and checkout screens use the same label for two different actions
  • A business with a new site or app where every button still carries placeholder text

Before you decide

When this may not be the right fit.

  • You need the full copy for a campaign page, including headline and proof. Landing page copywriting is the fitting service.
  • You need screens redrawn or the journey rethought before any wording is settled. UI/UX design comes first, and this service then supplies the words for the agreed screens.
  • You need the page built, tracked or connected to an inbox or CRM. Landing page development is the build, and it can take this copy sheet as an input.

The problem

Does this sound like your business?

Common situations this work addresses.

  • “Every button says Submit or Click here”

    The label names the mechanics, not the outcome. A buyer asking for a quotation, a patient booking a visit and a shopper placing an order all see the same word, and none is told what will happen after pressing it.

  • “Forms ask questions buyers cannot answer”

    A field label uses an internal term, such as a part code or a plan name, that the visitor has never seen. With no hint beneath it, the buyer guesses wrongly, abandons the form or sends an enquiry your team cannot use.

  • “Error messages blame the visitor and give no fix”

    Invalid input and Something went wrong tell the reader that a problem exists, not what to change. Buyers retry once, fail again and leave. Your team never learns that the enquiry existed.

  • “Confirmation screens leave the buyer unsure”

    After pressing send, the page says Done or simply reloads. The buyer does not know whether the request arrived, who will reply, or what to prepare. Repeat submissions and anxious calls follow.

Choose the right scope

Start with the work your business needs.

  1. One key action

    Wording for a single high-value step, such as request a quotation or book an appointment, covering the button, the form labels, the errors and the confirmation. Suited to a business that has one action that matters.

  2. A set for a whole site

    Consistent wording for every button, form and message across the site, with one tone note. Contact, newsletter, booking and basket screens all use the same terms for the same things.

  3. A refresh of existing wording

    We review the labels and messages already live, mark those that mislead or blame the visitor, and rewrite them. You receive a before-and-after sheet so your developer can change only what needs changing.

  4. A version for a second audience

    The same action can need different words for a trade buyer and a household buyer, or for a patient and a referring doctor. Each audience gets its own labels and messages, with the underlying facts kept identical.

What we do

The work we can include.

Each deliverable and the purpose it serves. Your written scope confirms what is included, who is responsible, and what it costs.

  1. Journey inventory

    A list of every screen, button and form in the agreed journeys, with the job each one does. You confirm that the list matches what buyers actually press before any wording is drafted.

  2. Call-to-action set

    Button, banner and closing-prompt wording for each agreed action, written to say what the buyer gets or what happens next. Your team approves any promise implied, such as a reply or a visit.

  3. Form field labels and hints

    Plain labels for every field, with a hint where the buyer might be unsure what to enter. Required and optional fields are marked in words, so the form asks only what your team will use.

  4. Error and validation messages

    Each message says what went wrong in the visitor's terms and what to do next. Your developer checks that every message matches a condition the form can actually produce.

  5. Confirmation and empty-state messages

    Wording for the moment after sending, for a basket or results list with nothing in it, and for a failed attempt. Each tells the reader what is happening and who acts next.

  6. Copy sheet for design and build

    One table listing every piece of wording, where it appears, the state it belongs to and any note for the developer. Your designer and developer enter it from the sheet, so nothing is paraphrased.

  7. Tone and wording notes

    A short note recording the voice used, the terms to prefer and the terms to avoid, so that wording added later by your team stays consistent with the delivered set.

How the result is measured

  • Enquiry forms started against forms completed
  • Form submissions your team can act on without a call back
  • Repeat submissions of the same request
  • Calls asking whether a request arrived
  • Error messages shown that the form can produce
  • Buttons still carrying placeholder or default wording

Recorded as a baseline before work starts, so every later report has an honest comparison.

Marketing and sales together

Your sales team receives enquiries that arrive with what they need.

The form labels are agreed with whoever replies to enquiries, so each field gathers something the team will use. The person handling the enquiry records which button or page brought it in, and whether the buyer had to be called back for missing details. That record shows which labels still fail and which are working.

Decisions to make before the work starts

  1. What this scope leaves out

    Screen layout, interface design, form building, tracking, split testing, translation and any change to the journey itself are separate scopes. The written scope names which of them, if any, sit beside the writing and who does each.

  2. What stays your decision

    You decide which actions to offer, what the business promises after a press, which fields are required and what is stored. Your named approver signs off any button or message that implies a reply, a visit, a price or an outcome.

  3. Where outside rules apply

    Consent, privacy and cookie wording comes from your adviser. Payment screens, app stores and form platforms set their own wording rules. Health, finance and education pages follow your regulator. We fit the copy to the current specification and your approved text.

This or a nearby service

Which piece of work fits your situation.

These services sit close to each other. The line between them, in plain words.

UI/UX design
Choose UI/UX design when the screens themselves need to be drawn or the path to an enquiry needs rethinking. Choose call-to-action and microcopy writing when the screens exist or are agreed and the words on buttons, labels and messages are the weak part.
Landing page copywriting
Choose landing page copywriting when a whole campaign page needs a headline, proof and an argument. Choose call-to-action and microcopy writing when the page is sound and the buttons, forms and messages need wording that tells the buyer what happens next.
Form and enquiry funnel optimisation
Choose form and enquiry funnel optimisation when the form's fields, order and routing need to be rebuilt and measured. Choose call-to-action and microcopy writing when the form's structure stays and its labels, hints and messages need rewriting.

A sample of the output

A copy sheet lists every piece of wording, where it appears and what it has to do.

The copy sheet is what your designer and developer work from. Read across a row for the element, the state it appears in, the wording to enter and the job that wording does.

Illustrative example, not client data. Yours is built from your own records.
Element and screenStateWording to enterJob the wording does
Main button on quotation formReady to sendSend my quotation requestNames the outcome instead of the mechanics
Quantity field labelEmpty, with hintHow much do you need? Give a rough amount if unsureLets a buyer without a number still proceed
Email field errorEntered address is incompleteThis address looks incomplete. Check the part after the at signSays what to fix, not that the buyer is wrong
Confirmation messageRequest receivedWe have your request. Someone from the sales team will reply to this addressTells the buyer who acts next
Basket screenBasket emptyYour basket is empty. Browse the range or ask us to suggest somethingGives the visitor a next move

Before we start

What we need from you.

The work depends on these. Each says why it is needed and what happens when it is missing.

Access to the live journey or a prototype
We need to walk through the screens as a buyer would, including the failed and empty states. If only a design file exists, tell us. Wording written without seeing the screens misses the states nobody drew.
The list of fields your team uses
Each form field should exist because someone on your team acts on it. We need that list, and an owner for the answers. Where it is missing, labels get written for fields that may later be removed.
What happens after each action
A confirmation can only promise what the business will do. We need the real next step for each action: who replies, through which channel, and what the buyer should prepare. An unconfirmed step is left out of the copy.
Your adviser's approved legal text
Consent, privacy and any mandatory declarations come from your own adviser. We place and label them but do not draft them. If the text is not ready, the sheet carries a clearly marked gap.
One person who approves the wording
A named approver resolves disagreements between design, sales and development. Without one, labels get argued screen by screen and the copy sheet is never marked final.

How it works

How the work runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Read your brief and the live journey

    We read your requirements brief and walk through the current screens as a buyer would. Together we agree which journeys the wording covers and who approves it.

  2. 2

    List every step where the visitor acts

    We record each button, field, message and state in the agreed journeys, including the ones nobody thinks about, such as a failed attempt or an empty result.

  3. 3

    Find what each step must say

    With your sales and support team we settle what the buyer needs to know at each step, what your team needs to receive, and which promises the business is willing to make.

  4. 4

    Write the wording

    We draft each label, button, hint and message in plain language, with the reader's task first. Where a message depends on a rule you have not decided, we mark it and ask.

  5. 5

    Review with design and build

    Your designer and developer read the draft against the screens and the form's real conditions. Wording that does not fit a screen or a condition is rewritten against the platform's current specification.

  6. 6

    Deliver the copy sheet

    You receive the approved sheet and the tone note. Entering the wording into the site or app is done by your team unless the written scope says otherwise.

Before you hire anyone

Do this first yourself.

Pressing through your own journey as a stranger would shows which words are failing before anyone rewrites them.

  1. Complete your own quotation, booking or basket journey on a phone, writing down every word you read.
  2. Deliberately make three mistakes in the form and note what each error message says.
  3. Highlight every button that says Submit, Send, Click here or Learn more.
  4. Ask your sales team which form answers they have to chase after receiving an enquiry.
  5. Write what really happens after someone presses send, then compare it with what the page says.

Judge any provider

What to ask any provider of this service.

Useful whoever you choose, including us.

  • How will you see the error and empty states, not just the main screen?
  • How do you decide what a button should promise, and who approves that promise?
  • Will you deliver wording in a sheet our developer can enter without paraphrasing?
  • What do you do when a label depends on a field we should probably remove?
  • Who drafts consent and privacy text, and where does your work stop?

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2 · you are here

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Who owns the finished wording and the copy sheet?
The written scope sets out ownership of the wording and the copy sheet, and which files you receive at handover. No ownership term is stated anywhere else. Ask for anything you want named, such as the tone note or the list of states, before work starts.
How are changes handled after we see the draft?
The written scope sets out how changes are made. Send comments through one named approver so conflicting views are settled first. A change that alters what a button does is referred back to your designer or developer, because it changes the journey, not just the words.
How are claims in buttons and messages approved?
A button that promises a reply, a visit or a price is a claim. Your named approver confirms each one against what the business will do. For health, finance, legal, education, real estate or food subjects, your own council, regulator or adviser decides the wording and any mandatory declarations.
Do you write consent, privacy and cookie wording?
We write the surrounding words, such as the label beside a tick box, but the legal text itself comes from your adviser or the platform you use. Consent and privacy wording is a legal matter, and we do not draft it. We place your approved text and check that the label reads clearly.
Can you test which button wording works better?
We can write variants of a call to action for you to compare, but running the test, setting up tracking and reading the results are separate scopes. We promise no uplift from any wording. Your own records of started and completed enquiries are the evidence to compare.
Does this include changing the form or the screen design?
No. This scope delivers wording only. Changing which fields a form has, redrawing a screen or building the form belongs to UI/UX design, landing page development or your own developer. If a field should be removed, we say so in the copy sheet and leave the decision to you.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.