Skip to main content
A project is the home for one app or website in Feddy. Everything that comes from that app lives inside it: the conversations, the people who wrote in, the topics users pick from, the answers Milo can give, and the settings that shape how Feddy looks and behaves. Each project has its own inbox. You’ll use projects to:
  • Keep each product’s conversations in their own inbox.
  • Decide who on your team can see which inbox.
  • Give each product its own branding, topics, and automatic answers.

​
One project per product

The usual setup is one project for each app or site you support. If you have an iOS app and a website for the same product, they can share a project as long as the same people answer both. Prefer two projects when you want separate inboxes.

​
The project ID

Every project has an ID that starts with fd_ followed by 16 characters. Copy it from Settings → Install. The SDK sends it with every message so Feddy knows which project, and which inbox, the message belongs to. The project ID isn’t a secret. It’s built into your app and visible in your page source, so anyone can find it, and that’s fine: it only identifies the project. Commit it, hard-code it, put it in a public repository. There’s no way to rotate it and no need to. If someone tries to flood your inbox, Feddy limits how many requests one device can send.

​
What’s inside a project

Everything below lives under Settings in the dashboard:
  • Install: the project ID, and copy-paste snippets for iOS, the web, and coding agents.
  • General: the project’s name and the short name used in its dashboard links, plus what users see: your brand name, accent color, and the response-time promise shown before and after they send a message. Pick the color from a short set or choose your own, and the response time from a list that already reads in every language users see. A preview beside the settings shows the result as you change it; your app picks it up once you save.
  • Topics: the choices users pick from when they start a conversation.
  • Data attributes: the facts you send about users, such as their plan, and how they appear in the inbox.
  • Milo AI: automatic replies, and the answers they’re allowed to draw on.
  • Saved replies: snippets you can drop into the reply box by typing /.
  • Email domain: the domain your replies are emailed from.
  • Members: who can see this project’s inbox.
  • Danger zone: archive the project, or delete it and every conversation in it.

​
Development and production

You don’t need a separate project for testing. The SDK has an apiUrl option for pointing a development build at a local server, and the project ID stays the same either way. Create a second project only if you’d rather keep test conversations out of your real inbox.

Create a project

Sign up, create your first project, and copy its ID.

Conversations

What arrives in a project’s inbox and what happens to it.

Milo

Set up automatic answers for the questions you get most.

Team

Invite teammates to a project and connect an email domain.