---
name: ivr-documents
description: Create IVR Cloud Word documents using the supplied Pandoc reference and generate PDF documents directly from Markdown with XeLaTeX.
---

# IVR Cloud documents

Use independently. Editable DOCX requires Pandoc 3.x; PDF additionally requires XeLaTeX and its LaTeX packages. Install the supplied **Inter** desktop fonts first. Code uses **DejaVu Sans Mono**, available separately from the system font packages. Web font CSS does not install desktop fonts.

## Brand and document decisions

IVR Cloud helps businesses configure telephone menus, phone routes, contacts, campaigns, call history, and voicemail. Use IVR Cloud on first mention. Write calmly and precisely; invent no integrations, pricing, customer evidence, uptime, or certifications. Match the requested locale and preserve Romanian diacritics.

Keep **draft**, **published version**, and **deployed route** distinct. Publishing creates an immutable version; deployment changes the phone route. Label example records and diagrams as fictional. Separate observations, interpretation, recommendations, and open questions.

The reference uses A4, 1-inch margins, Inter 28pt title / 12pt subtitle / 16–13–11pt headings / 11pt body / 9pt captions. Forest #1F7558 carries headings/links; Ink #14231F carries body text; supporting text is #65726C. The first-page header contains the IVR symbol and name; the later header uses a Word TITLE field. A page-number footer is included. No unconditional Confidential label is added.

Plan for the reader's decision: purpose, supplied evidence, scope, recommendation, and next action where useful. This is a starting pattern, not a required section sequence. Keep tables narrow, images captioned, and technical detail in an appendix when it interrupts the main point.

## Resources

Links are absolute so this skill works as a single supplied file. Resources use the fixed https://brand.ivr.ro/ address, independently of local preview settings. Download only needed assets; a toolkit ZIP is not required. In a local checkout, use `templates/`, `examples/`, and `brand/` from the root.

- [Word reference](https://brand.ivr.ro/downloads/templates/documents/ivr-document-reference.docx)
- [PDF header styling](https://brand.ivr.ro/downloads/templates/documents/ivr-document.tex)
- [Example Markdown](https://brand.ivr.ro/downloads/examples/report.md)
- [Example illustration PNG](https://brand.ivr.ro/downloads/examples/ivr-workflow.png) and [SVG source](https://brand.ivr.ro/downloads/examples/ivr-workflow.svg). Save the PNG as `ivr-workflow.png` beside `report.md` when using the example.
- [Inter 400](https://brand.ivr.ro/brand/assets/fonts/Inter-400.ttf), [500](https://brand.ivr.ro/brand/assets/fonts/Inter-500.ttf), [600](https://brand.ivr.ro/brand/assets/fonts/Inter-600.ttf), [700](https://brand.ivr.ro/brand/assets/fonts/Inter-700.ttf), [800](https://brand.ivr.ro/brand/assets/fonts/Inter-800.ttf), [license](https://brand.ivr.ro/brand/assets/fonts/LICENSE.txt)

## Write Markdown

```markdown
---
title: Planul fluxului de apel
subtitle: Versiuni, rutare și verificări
author: IVR Cloud
date: 13 October 2026
---

# Scop

Descrie rezultatul și sursele furnizate.

## Versiuni

| Stare | Versiune | Efect |
|:---|:---|:---|
| Ciornă | v4 | Editabilă |
| Publicat | v3 | Disponibil pentru deployment |
| Activ pe rută | v2 | Folosit de ruta demonstrativă |

: Date fictive, folosite pentru ilustrarea stilului

::: {custom-style="Callout"}
**Decizie necesară.** Numește ruta și versiunea propusă pentru activare.
:::
```

Use `#`/`##`/`###` for heading hierarchy. The reference includes the paragraph style `Callout` and character style `Label`; custom Word formatting does not automatically carry into direct PDF output. A reference supplies styles and page settings, not its sample body.

Use footnotes for source detail. Keep long links and code within the page width. Static PNG/JPEG images are predictable across Office and PDF. Export a diagram before conversion; Pandoc does not automatically render Mermaid or interactive charts.

## Generate DOCX

Download the reference as `ivr-document-reference.docx` into the folder with `brief.md`, or use its existing local path:

```sh
pandoc "brief.md" --from=markdown --standalone \
  --reference-doc="ivr-document-reference.docx" --resource-path=. \
  --output="ivr-brief.docx"
```

Modify named styles in Word/Writer for reusable changes. Changing the paper size or Word styles does not change the independent PDF styling file. Refresh the TITLE field when opening the final document if needed.

## Generate PDF directly

Use XeLaTeX from TeX Live, MiKTeX, or MacTeX. On Debian/Ubuntu, typical PDF prerequisites are `texlive-xetex`, `texlive-latex-extra`, `texlive-pictures`, and `texlive-fonts-recommended`. Check `pandoc --version` and `xelatex --version`; install tools only within the user's authorization.

Download the header as `ivr-document.tex` beside the Markdown:

```sh
pandoc "brief.md" --standalone --pdf-engine=xelatex \
  -V mainfont="Inter" -V monofont="DejaVu Sans Mono" \
  -V fontsize=11pt -V papersize=a4 -V geometry:margin=1in \
  --include-in-header="ivr-document.tex" --resource-path=. \
  --output="ivr-brief.pdf"
```

This renders PDF directly from Markdown. It does not need the DOCX reference, LibreOffice conversion, or a helper script. Word and XeLaTeX use separate layouts; do not promise matching pagination, Word callout shading, or identical header artwork.

## Inspect and deliver

Check every page for titles, fonts, source claims, heading placement, table wrapping, captions, footnotes, page numbers, and clipping. Keep tables editable and labels meaningful. Inspect DOCX in the intended Office application when available; a ZIP/XML check alone is not visual validation. Inspect selectable PDF text and embedded fonts when tools allow; this alone does not establish accessibility conformance.

Deliver requested editable/PDF formats and Markdown when useful. If tools/fonts are missing, provide usable Markdown and the exact missing prerequisite instead of claiming a finished export. Report unavailable Microsoft Word checks separately from native generation and PDF inspection.

The `ivr-brand` skill is optional for broader identity decisions. Technical references: [Pandoc reference documents](https://pandoc.org/MANUAL.html#reference-doc), [PDF generation](https://pandoc.org/MANUAL.html#creating-a-pdf).