Customer communications
ByteDocsByteDocsYour customer communications, built properly.
ByteDocs is our own CCM platform. It turns your customer data into personalised letters, statements and notices, as PDF for email and archive or AFP for the print room. Write the wording once, design the page once, and let the data decide what each customer gets.
Sound familiar?
What it does
Group documents into applications (savings in one, mortgages in another) and have as many documents in each as you need. A rule on each document decides which customers get it, from a document ID in the data, a flag, or a calculated value.
Set up an address page with the logo, address window, date and footer, then build any page from it. Change the template and every page that uses it follows, in every application. A4, A3, A5 or US sizes, portrait or landscape.
Standard terms, footers, regulatory text and commercial wording live in one library and are shared by every application. Rules on paragraphs and sections decide who sees what, and anything can be kept to a single application when it needs to be.
Pick any paragraph, template, variable or data field and see every document it reaches, and how it gets there. You know the impact of a change before you make it, which is most of the battle in BAU.
CSV, JSON or XML. Mark where each customer starts, link fields to variables and set up repeating lists such as policies or transactions. A data layout can be shared by several applications, so a standard feed is mapped once.
Calculated variables work out what the data doesn't hold: totals, price changes, salutations, which document to send. A small script language with IF, SELECT CASE, loops and over 60 functions, checked as you type.
Authors draft, approvers approve, with a word-by-word comparison and a date the change goes live. Runs only use approved wording. Test runs include drafts and are watermarked so they can't go out by mistake.
Embedded fonts and logos in the PDF, and AFP print streams with an indexed page group per customer, the documents each one received, and mixed paper sizes. There's an AFP viewer built in for checking print files.
A closer look
The demo uses Fenmoor Mutual, a made-up insurer, with two applications: renewal packs from XML, JSON or CSV, and claims letters chosen from a DOC_ID in the claims extract.
Draw the areas once in millimetres. Every page built on the template stays linked to it.
One paragraph, four documents, two applications, and the route to each. You see the impact before you change a word.
Write a paragraph once, decide who it applies to, and use it anywhere. Approval and version history come with it.
Point at where each customer starts and link fields to variables. Other applications can use the same layout.
Every customer gets every document their data qualifies for, as PDF or AFP, with a report of who got what.
How it works
Load a sample of your feed, mark where each customer starts and link the fields you need.
Design the page templates, then write or import the paragraphs and sections, with their rules.
Add pages from the templates, place the content and say which customers get each document.
Changes are approved before they go live. Runs produce PDF or AFP with a full report.
We'll take you through the demo, ideally with one of your own letters, and talk honestly about where it would fit.
Built from the ground up, from real experience. ByteDocs comes from twenty years of building and migrating documents on client sites. Read how it started, or see the consultancy work we still do every day.