- A user writes in. They tap Support in your app, or the chat button on your site, and send a message.
- You see it in your inbox. The message arrives with the user’s device details and anything you’ve told Feddy about them, so you can answer without asking follow-up questions.
- Your reply reaches them. It appears in the app or on the site, with a badge so they notice it. If you’ve connected an email domain, they get it by email as well.
Before you start
You’ll need a Feddy project and its project ID. Both take a minute, and the free plan covers everything in these docs.Create a project
Sign up, create a project for your app or site, and copy its project ID.
Set up with an AI agent
Prefer to let Claude Code, Cursor, or another coding agent do the install? Start here.
Add Feddy to your product
Pick your platform. Each page takes about five minutes and ends with a real message in your inbox.iOS
SwiftUI
A Swift package and a Support row.
UIKit
The same package, from your app delegate.
Web
JavaScript
One script tag, nothing to build.
React
A small component and your own button.
Vue
Load on mount, open from a button.
Svelte
Load on mount, open from a button.
Next.js
Once in the root layout.
Astro
Two lines in your shared layout.
WordPress
From your theme or a small plugin.
Webflow
Paste into Site settings and publish.
Learn how it works
Once messages are coming in, these pages explain what you’re looking at in the dashboard and what you can do with it.Projects
What a project holds, and why its ID is safe to share.
Conversations
What a thread contains, what its status means, and what happens on its own.
Contacts
Who’s writing in, from an anonymous visitor to a user you’ve identified.
Assistant
Automatic answers to repeat questions, and a Copilot that drafts replies for you.
Team
Inviting teammates, getting notified, and sending replies by email.
Go further
Identify users
Tell Feddy who’s logged in, so you see their name in the inbox and replies can reach them by email.
Unread badge
Show a count on your Support button so users notice when you’ve answered.
iOS SDK reference
Every call in the Swift package, with its signature and what it does.
Web SDK reference
Every option and call in the web widget.
Troubleshooting
What to check when something doesn’t behave as expected.