Skip to main content
Feddy is built for a small team answering together: one inbox, everyone sees the same conversations, and a reply from any of you reads as a reply from the product. This page covers who can see a project, how you’re told about new messages, and how your replies travel.

​
Members

A project’s Members page lists who can see its inbox. There are two roles:
  • Owner: every project, plus members and billing.
  • Member: this project’s inbox only.
Invite people by email. An invitation is good for 7 days. Owners can disable a member without removing them, which keeps their history in place, and restore them later.

​
Notifications

Everyone chooses their own under Account → Notifications.
  • Email: a message for each new conversation and reply, either right away or bundled every 30 minutes, 3 hours, or 12 hours.
  • Dashboard: a sound when a message arrives, the unread count in the browser tab’s title, and desktop notifications while you’re away from the tab. Desktop notifications are a per-browser setting, so switch them on in each browser you use.

​
Replies by email

Replies always appear inside your app or site. They also go out by email when two things are true: Feddy has an email for the contact, and your project has a verified email domain. To set one up, go to Settings → Email domain, add a subdomain of your own such as support.yourapp.com, and publish the DNS records shown there. Once the domain is verified, replies go out from your own address, with the full reply in the body so the user can read it without opening the app. Until then, replies are shown only in the app, and the SDK doesn’t ask users for an email, since there’d be nothing to send.
Feddy never emails your users from a Feddy address. Mail to you and your team, such as notifications and invitations, comes from Feddy’s own domain; mail to your users only ever comes from yours.

​
Saved replies

Settings → Saved replies holds the answers you send often. Give one a shortcut, then type /shortcut in the reply box to drop it in.

Identify users

Pass a user’s email so replies can reach them once your domain is verified.

Contacts

Where a contact’s email comes from and how it’s used.

Conversations

Replies, notes, and what counts as unread for your team.

Milo

Let Milo handle repeat questions so your team sees fewer of them.