Our editorial standards: how Mediahawk produces, reviews and corrects its content

Trust is important. That’s why we’ve put together this guide on how our content is made, who writes it, how we check it, and what we do when we get something wrong.

In short:

• Our content is written by named people on the Mediahawk team and our copywriting partner, Radix Communications, not anonymous freelancers
• Every page goes through a set review before it’s published
• We check facts, figures and product claims against original sources
• We review pages on a fixed schedule and update them when things change
• If we make a mistake, we fix it openly and show when each page was last reviewed

Who writes our content

Everything we publish is written or reviewed by named members of the Mediahawk team and our copywriting partner, Radix Communications. You won’t find ghost-written filler here, and we don’t outsource our guides to writers who’ve never used the product.

Our content strategy is overseen by our Head of Marketing, Faye Thomassen, and led by our Marketing Manager, Karina Bikerniece. Karina has a wealth of marketing experience and a Master’s in Marketing and Advertising. Their combined deep knowledge and everyday experience of marketing means we really understand your challenges and are dedicated to helping you succeed through value-added content.

Technical content, like our guides to call attribution, dynamic number insertion and speech analytics, is reviewed by Martin Stevens, our Development Manager. They know the product inside out, so they catch the things a general writer might miss.

Each author has a profile page so you can see who they are and what they know. For example, CEO, Michael Morrell, Director, Harry Bott, and Head of Marketing, Faye Thomassen.

How we review content before we publish it

No page goes live on a whim. Each one runs through the same steps first.

• A brief sets out the purpose, audience, key message, and the main points the content has to cover
• An author writes the draft
• An editor reviews it for accuracy, clarity and tone
• Where the page makes a product or feature claim, the relevant team checks it’s correct
• A final sign-off happens before anything is published

If we ever run guest blogs written by our partners, we label them clearly so you always know what you’re reading. Guest blogs go through the same process as our other content to ensure the same high quality and that it always provides value to our readers.

How we keep our content accurate

We check facts, figures and product claims against original sources before a page is published. That’s the rule, and it’s a simple one.

For us, an original source means our own product data, our product and engineering teams, official documentation from platforms like Google, or named industry research that we link to. If we quote a statistic, we’ll tell you where it came from.

Products and prices change, so we revisit pages that mention them and keep the details up to date.

We’ve been building call tracking since 2002, we’re a Google Cloud Partner, and we work with marketing attribution, call tracking, and speech analytics every day, so the people checking these claims actually know the subject.

How often we update our content, and how we fix mistakes

We review our content on a regular cycle. For our feature pages, it’s when a product has changed; for blog content, it’s between 12-18 months. Everything else is when an update is required.

Each page shows when it was last reviewed, so you can see how fresh the information is. If something’s changed since you last looked, you’ll know.

We get things wrong sometimes, and when we do, we’d rather hear about it. Spot an error? Tell us, and we’ll look into it. We correct significant mistakes openly rather than quietly editing the page and hoping nobody noticed.

Contact our editorial team

If you’ve found a factual error, or you’ve got a question about how we put our content together, get in touch via our Contact us page. We read every message, and we’ll come back to you within 5 working days, if required.