Customization
Adjust branding, copy, and interface details in minutes. RealReply is built for simple customization without architectural changes.
Customizing RealReply
RealReply is intentionally simple to customize.
It’s just a Next.js app you own. No hidden SaaS layer. No remote theming service. If you can edit a React component, you can customize RealReply.
This page covers small, safe changes — branding, copy, and UI tweaks — without touching the core support logic.
1. What You’re Customizing
RealReply is built to make minor changes easy.
You are typically adjusting:
- Branding (logo, colors, app name)
- Copy (labels, headings, empty states)
- Light UI details (button styles, layout spacing)
You are not expected to rewrite infrastructure, ticket logic, or storage. Most teams can fully align RealReply with their product in under an hour.
2. Prerequisites
Before customizing:
- Make sure you've done all the steps in the [Quickstart]
Create a local development environment file:
cp env.example .env.development.local
Edit the new file and enter your environment variables.
3. Running in development mode
There are two workers and technically only one (the Next.js app) is required, but you should run both.
In a terminal, run the websocket worker:
npm run ws
In a second terminal, run the Next.js worker:
npm run dev