A PR team's guide to the Devotel Orbit press kit: assets, guardrails, and the release-sync loop

The press kit exists so a journalist, analyst, or partner can describe Devotel Orbit correctly without a sales call. But the kit is a destination — a page you land on, pull files from, and leave. What there has never been is an editorial walkthrough of how a PR team should actually use it: which variant goes where, which naming rule is non-negotiable, how to handle localization, and how to stop a three-release-old boilerplate quote from circulating. This post is that walkthrough — the editorial anchor any trade-press outreach on this team should point at.

What the press kit actually ships

Open the Devotel Orbit press kit (or the docs version of the same rules) and the inventory is finite — four asset classes and one routing contact:

• Logomark variants. Two full logo files and two mark-only files, all SVG.

The colored logo is for light surfaces; the white logo is for dark surfaces; the mono logomark is the fallback when only one ink is available. Both composition forms solve the light/dark problem deliberately — a press team should never need to recolor anything.

• Approved boilerplate, verbatim. The company description at three

lengths — ~80 words for captions and listings, ~160 for reviews and analyst notes, ~320 for funding or profile coverage. Every length is pre-approved; quote it exactly or don't use it at all. A non-standard length is a press-desk request, not an editing task.

• Founder bio and company facts. Erol Fedakar, founder; Devotel UK LTD,

in operation since 2025; a licensed telecom operator that owns its own voice softswitch; Istanbul headquarters with a globally distributed engineering team. Facts a piece can cite without a briefing call.

• Media inquiry routing. One address: press@devotel.io. Anything that

is not on the page — a quote, an interview, a non-standard-length boilerplate, an embargo question — goes through the press desk, not through sales.

The discipline this imposes: pull from the kit, not from a screenshot of the site, and not from last quarter's deck. The assets above are the whole surface; anything beyond them is a press-desk conversation.

Brand guardrails a PR team must honor

Two rules are non-negotiable, and the first one is the one that most drafts violate:

• The full product name is "Devotel Orbit." Bare "Orbit" is fine inside a

sentence once the full name is established — but never in a headline, a deck title, or a link anchor. "Devotel Orbit" in every title; bare "Orbit" only in running text.

• "Orbit.com" is never written. Devotel does not own that domain. The

product lives at orbit.devotel.io and the company at devotel.io — inventing a different orbit-* domain is the most common press error and does real damage to search attribution.

Do/don't in practice:

• Do keep the logo's aspect ratio as delivered; never stretch, redraw, or

recolor the mark.

• Do use the colored logo on light surfaces and the white logo on dark

ones; fall back to the mono logomark when only one ink prints.

• Don't write "Devotel Orbit platform by Devotel" or any re-styled

variant of the name — the approved name is the full name, exactly once.

• Don't paraphrase the boilerplate. If a piece needs phrasing the

boilerplate doesn't cover, the press desk cuts a new approved length; editorial-safe improvisation is not a trade-off to make.

These rules are on the kit itself and on the docs page; this guide exists because a rule on an assets page gets read once, while a checklist in a usage guide gets enforced.

Localization across the six locales

The press kit renders in the six locales the product ships — English, Turkish, Arabic, German, French, and Spanish — and the URL pattern is locale-prefixed: /en/press-kit, /tr/press-kit, /ar/press-kit, and so on. Three rules keep localized coverage from going wrong:

1. Pull assets from the locale the piece targets. The SVG files

themselves are locale-independent, but boilerplate and facts panels are translated per locale; a Turkish-language piece that quotes the English boilerplate is a mismatched pull.

1. The naming rules do not localize. "Devotel Orbit" is written the same

in every locale, including in Arabic-script copy; the full-name rule is a brand invariant, not an English-language convention.

1. Press-desk routing does not localize. press@devotel.io is the

routing address regardless of the journalist's working language; the desk responds in the language the inquiry arrives in.

Chain-of-custody: keeping press assets in step with product releases

The failure mode a PR team actually hits is not a wrong logo — it is a boilerplate paragraph quoted six months after the copy changed. The fix is a loop, not a rule:

1. Watch the changelog and the announcements hub. Every changelog entry

and every announcement post on /announcements that touches positioning, naming, coverage, or company facts is a candidate press-kit refresh trigger. The marketing side of the house owns the boilerplate text; the product side owns the facts.

1. Re-pull assets on every positioning change. When a release changes

what the product is — a new pillar, a new coverage claim, a renamed capability — the press kit's boilerplate and facts panel are re-cut in the same cycle. A PR team that re-pulls after each such release never ships a stale description.

1. Version the pull, not the kit. Every asset the kit ships is SVG at a

stable public path, so "sync" for a PR team means: record the pull date in the outreach doc, re-pull on positioning releases, and re-quote the boilerplate verbatim rather than carrying forward last cycle's copy.

1. Emergency corrections go through the press desk. If a circulating

quote is wrong — a stale boilerplate, a misnamed product — the press desk issues the corrected length and the correction note; a PR team does not silently update its own copy.

Frequently asked questions

Can we edit the boilerplate for length or tone?

No — quote one of the approved lengths verbatim. Every length is pre-approved as-is, and paraphrasing the company description is the correction cycle's most common trigger. If none of the three lengths fits the piece, email the press desk at press@devotel.io and a new approved length will be cut for you.

Can we crop or restyle the logo for a specific layout?

No. The kit ships the colored logo for light backgrounds, the white logo for dark backgrounds, and the mono logomark for single-ink contexts; one of those three covers every realistic layout. Cropping, redrawing, stretching, or recoloring the mark is a usage violation regardless of intent.

Which name do we use in a headline — "Orbit" or "Devotel Orbit"?

Always "Devotel Orbit." Bare "Orbit" is acceptable only in running text after the full name has been established once; headlines, deck titles, and link anchors use the full name every time. The same rule holds across every locale.

How do we keep quoted facts current across releases?

Watch the changelog and the announcements hub for anything that touches positioning, coverage, or company facts, and re-pull the press kit after each such cycle. The kit's boilerplate and facts panels are re-cut in the same release cycle, so a fresh pull after a positioning release is the whole workflow.

What if a name, fact, or asset we need is not on the press kit page?

Route it to the press desk at press@devotel.io. The kit is deliberately a finite surface — anything beyond logos, boilerplate, facts, and founder bio is a desk conversation, not an improvisation.

Where this fits

If you are the PR team this guide is written for: the assets live on the press kit, the same rules in docs form live at docs, company background lives on /about, and anything not covered above goes to /contact or straight to the press desk. This post is the anchor trade-press outreach should link to — a usage guide, not just a download page, is what makes the kit usable at press cadence rather than once.