Formulating Text Messages In Novels: Complete Formatting & Style Guide

Integrating SMS exchanges into a manuscript requires balancing narrative clarity, industry typesetting standards, and cross-platform display compatibility. Authors must choose between inline integration, block-indented text threads, or custom CSS styling while adhering to Chicago Manual of Style guidelines and EPUB reflow standards. Mastering these formatting techniques ensures seamless visual transitions between traditional dialogue and modern digital communications across both print and digital formats.

Manuscript Layout Prerequisites & Typographic Standards

Before integrating digital messaging into a book manuscript, authors and interior layout designers must establish clear typographic rules and structural constraints. Text messages interrupt traditional narrative flow, meaning their formatting must clearly signal a medium shift without breaking visual coherence or causing rendering errors during digital distribution.

Essential Gear, Tools, and Software

• Manuscript Editors: Microsoft Word (using defined Style Sheets), Scrivener (using Compile presets), or Atticus.
• Professional Typesetting Software: Adobe InDesign (for print layout PDF generation) or Vellum (for automated EPUB/print conversion).
• Font Packages: Licensed screen-optimized sans-serif typefaces (such as Helvetica Neue, Arial, or Courier Prime) paired with standard narrative body fonts (such as Garamond, Sabon, or Baskerville).

Prerequisite Knowledge & Editorial Standards

• Style Guide Compliance: Adherence to The Chicago Manual of Style (CMOS 17th Edition, Sections 13.43 and 11.145) for short-form digital communication, or Associated Press (AP) Style for journalistic non-fiction.
• Digital Publishing Specifications: IDPF EPUB3 reflowable text standards and Amazon Kindle Direct Publishing (KDP) reflowable formatting rules.
• Accessibility Guidelines: Web Content Accessibility Guidelines (WCAG 2.1 AA) for digital e-readers, ensuring high-contrast rendering and screen-reader compatibility.

Project Benchmarks

• Estimated Execution Time: 2 to 4 hours for manuscript-wide style sheet setup and global search-and-replace tagging.
• Financial Investment: $0 (using native word processor styles) to $250 (for specialized typesetting tools or custom SVG icon licenses).

Step-by-Step Workflow for Rendering Text Messages in Fiction

Step 1: Select the Appropriate Structural Format

Determine whether the text message requires inline integration or a block-indented display format based on length, narrative weight, and frequency.

1. Inline Formatting: Use inline styling for brief, single-sentence text messages or quick notifications that occur within standard prose paragraphs. Enclose the text in quotation marks or render it in italics, accompanied by an explicit attribution tag (e.g., She glanced at her phone; the message read, "Meet me at eight.").
2. Block-Indented Display: Use block-indented formatting for back-and-forth multi-line text exchanges, rapid conversations, or threaded interactions. Isolate the text thread from the main body paragraphs using a double line break above and below the sequence.
3. Graphic Image Displays: Reserve visual chat bubbles saved as PNG or SVG graphic files strictly for special print editions. Avoid image-based text messages in reflowable e-books, as images break custom font scaling, fail dynamic light/dark mode transitions, and degrade low-resolution displays.

Pro-Tip: For e-book stability, avoid using graphic image bubbles for text threads. E-readers allow users to adjust font size and line spacing; static image bubbles will fail to scale proportionally, leading to illegible text or awkward page breaks.

Step 2: Establish Typographic Rules and Visual Cues

Differentiate digital communications from spoken dialogue by applying distinct typographic treatments.

1. Font Family Substitution: Shift from the primary serif body font (e.g., Georgia 11pt) to a clean, sans-serif font (e.g., Arial 9.5pt or Courier 10pt) for the text message thread to mimic a mobile phone display.
2. Alignment & Indentation:
   
   
   • Set a left indent of 0.5 inches and a right indent of 0.5 inches for the entire text block to detach it from main paragraph margins.
   • To replicate mobile messaging interfaces, left-align incoming messages (received) and right-align outgoing messages (sent).
3. Character Name Identifiers: Prefix each message line with the sender’s name or phone number rendered in bold small caps (e.g., MARK: or UNKNOWN NUMBER:) followed by a colon and a single space.

Warning: Do not rely solely on color (such as blue or green message bubbles) to differentiate senders. Over 80% of dedicated e-readers (such as the Amazon Kindle Paperwhite) utilize monochrome E-Ink screens, rendering subtle color variations as identical shades of gray.

Step 3: Standardize Timestamps, Headers, and System Notifications

Contextual meta-information—such as timestamps, read receipts, and system alerts—must be standardized using consistent formatting rules across the entire manuscript.

1. Timestamp Centering: Format date and time headers in small caps, centered above the text message thread, using a reduced font size (1 to 2 points smaller than the body text). For example: THU, OCT 12, 10:42 AM.
2. System Status Messages: Format system-generated alerts—such as [Delivered], [Read 11:05 AM], or [Typing...]—in bracketed italics, right-aligned directly beneath the corresponding message line.
3. Emoji Management: Replace dynamic color emojis with standard Unicode glyphs or descriptive textual bracket placeholders (e.g., [thumbs up emoji] or [grimacing face]). Standard print production workflows cannot reliably translate full-color mobile emoji sets without causing font-embedding errors during High-Definition PDF output.

Step 4: Configure Word Processor Styles for EPUB and Print Layouts

Rather than manually applying spaces, tabs, or font tweaks to every text message line, build reusable style templates within your word processor to maintain semantic HTML export integrity.

1. Create an Incoming Text Style:
   
   
   • Font: Sans-Serif (Arial or Courier), 9.5pt.
   • Alignment: Left-aligned.
   • Space Before: 3pt; Space After: 3pt.
   • Indentation: Left 0.5 inches, Right 1.5 inches.
2. Create an Outgoing Text Style:
   
   
   • Font: Sans-Serif (Arial or Courier), 9.5pt.
   • Alignment: Right-aligned.
   • Space Before: 3pt; Space After: 3pt.
   • Indentation: Left 1.5 inches, Right 0.5 inches.
3. Apply Clean Paragraph Breaks: Ensure soft returns (Shift + Enter) are avoided within message blocks. Use explicit hard paragraph returns (Enter) paired with configured style sheet spacing to prevent formatting collapse during conversion to EPUB formats.

Step 5: Execute Proofreading and Cross-Device Rendering Audits

Verify that the text message formatting retains its visual integrity across multiple print outputs and digital devices.

1. Export to EPUB and Mobi/KFX: Generate a test digital compilation file from your master manuscript.
2. Test across Reading Platforms: Load the file onto an E-Ink device (Kindle Paperwhite), a tablet (iPad Kindle app/Apple Books), a mobile phone screen, and a desktop reader.
3. Verify Reflow Compliance: Increase the font size to maximum settings on the target device. Check that text bubbles, indents, and character labels do not wrap erratically, force single words onto isolated lines, or clip off the display margins.

Technical Formatting Matrix across Publishing Mediums

Common Formatting Pitfalls & Typesetting Fixes

EPUB Line-Break Collapsing and Margin Clipping

• Root Cause: Word processors often export manual tab indents and multiple spaces as non-breaking space strings, which modern EPUB renderers collapse into a single space line. This strips right-aligned outgoing messages of their margin offsets, dumping all text against the left edge.
• Actionable Fix: Remove all manual spaces and tab stops. Create dedicated paragraph styles using explicit percentage-based or em-based margins in your e-book layout software (e.g., margin-left: 15%; margin-right: 5%;).

Broken Emoji Rendering and Missing Characters in Print PDF

• Root Cause: Modern smartphone emojis rely on specialized system color fonts (such as Apple Color Emoji or Segoe UI Emoji) that cannot be embedded into standard PDF/X-1a print files required by print-on-demand services like KDP or IngramSpark.
• Actionable Fix: Convert emoji symbols into clean 1-color vector silhouettes (SVG or EPS format) placed inline as anchored graphics, or replace them with italicized bracketed text descriptions (e.g., [heart emoji]).

Text Message Thread Splitting Over Page Breaks

• Root Cause: Automated typesetting engines may insert an automatic page break in the middle of a short two-line text exchange, leaving an isolated sender header at the bottom of a page (orphan) and the reply at the top of the next page (widow).
• Actionable Fix: Apply a "Keep with Next" or "Keep Lines Together" paragraph rule to the text message CSS styles or word processor style definitions. This forces the engine to move the entire text sequence onto the subsequent page if there is insufficient vertical space.

Inconsistent Dialogue Tags and Punctuation Placement

• Root Cause: Authors frequently mix traditional spoken dialogue conventions (such as placing speech tags inside quotation marks) with text message threads, causing reader confusion regarding whether a line was spoken aloud or transmitted digitally.
• Actionable Fix: Maintain a strict separation of styles. Omit traditional quotation marks when using block-indented text threads with character headers (NAME:). Reserve quotation marks exclusively for spoken dialogue or inline text message quotes embedded within standard narrative prose.

Frequently Asked Questions

What is the Chicago Manual of Style rule for formatting text messages in novels?

The Chicago Manual of Style recommends treating short text messages similarly to direct quotations or letters. Brief messages can be set inline within quotation marks or italics, while longer exchanges should be formatted as block quotations set in a distinct sans-serif typeface to visually reflect a screen interface.

Should you use images of text bubbles in a self-published e-book?

No, using image files to represent text bubbles in reflowable e-books is strongly discouraged. Images do not adjust to a reader's chosen font size, fail on dark-mode screen settings, increase overall file delivery fees on platforms like Amazon KDP, and create accessibility hurdles for vision-impaired readers using screen-reading technology.

How do you format emojis within a printed book manuscript?

Emojis should either be converted into high-contrast single-color vector graphics embedded inline with the text or translated into plain text descriptions enclosed in square brackets. Standard multi-color mobile emojis will fail print pre-flight checks because their color profiles cannot be embedded into standard print-ready PDF files.

Do text messages in novels require traditional dialogue tags like "he said"?

No, block-formatted text messages generally do not require spoken dialogue tags like "he said" or "she texted." Senders are typically identified using bold character headers, phone numbers, or contact labels at the start of each line, mirroring the interface of an actual mobile messaging app.

Elevate Your Manuscript's Visual Narrative

Structuring digital communications with precise typography ensures your manuscript remains clean, readable, and visually engaging across both print and digital formats. Apply these structural guidelines and standardized style sheets to transform your book's modern dialogue into a polished, professional reading experience.