Getting started
These are the steps to start using Support Node. Support Node is in closed beta, and usage is approved per organization.
1. Create an organization
Support Node works per Cyberneura ID organization. Create an account on Cyberneura ID and create an organization. Invite the teammates who handle inquiries with you to that organization from Cyberneura ID.
When you log in, your organizations are brought into Support Node. Only organization owners can change organization settings (such as the AI settings).
2. Apply for the beta
Log in to Support Node with your Cyberneura ID. Your organizations are imported and an "under review" screen appears; as it says, let us know through the contact page that you would like to use the service.
During the beta, organizations need approval. You can log in with any email address, but until your organization is approved you will see an "under review" screen instead of the admin screens. Once it is approved, press "Check status" on that screen to open the dashboard.
3. Set up a sending service and domain
To send replies, you need an account with one of these email delivery services. Sending through an SMTP server such as Gmail or Outlook is not supported.
- Brevo (formerly Sendinblue)
- SendGrid
- Mailgun
- Register the domain you send from (for example,
example.com) with the service, and add the SPF and DKIM records it gives you to your DNS. Set up a DMARC record as well. Without them, replies tend to land in spam or get rejected. - Create an API key on the sending service.
- In the Support Node admin screens, open "Email accounts" and register the sender address, the service, and the API key (for Mailgun, enter the domain name in the account ID field). Then use the test send to confirm that messages arrive.
4. Create templates and a project
- In "Templates", create one first email template, one reply email template, and one AI prompt. A project cannot be created without all three (the AI prompt is required even if you do not use AI drafts).
- To get new inquiries in Slack, register a Slack incoming webhook URL in "Notification webhooks".
- In "Projects", create a project for each support inbox. Select the email account from step 3, the templates and AI prompt you just created (and the notification webhook).
- To close quiet threads automatically, edit the project and set "Auto close N days after a reply" (the default, 0, turns this off). A customer reply moves the thread back to "Reply received".
5. Bring in inquiries (email forwarding)
Each project has a receiving address in the form below. The actual address is shown as "Email address for thread replies" in the "Projects" list in the admin screens.
project-<project ID>@support.cyberneura.net
Set up forwarding on your mail server or mail service so that
messages sent to your current support address (for example, support@example.com) are forwarded to this address.
Forwarded messages become threads, and replies are sent from the
email account in step 3.
6. Register from a web form (webhook)
Instead of email, you can register threads directly from the contact form on your website.
- In the project's "API keys", create an API key with the message receiving permission.
- Copy the webhook URL from the "Projects" list and POST JSON to
it from your server. Pass the API key in the
Authorization: Bearer <API key>header.
POST https://support.cyberneura.net/api/webhook/support-thread/create/<project ID>
Authorization: Bearer <API key>
Content-Type: application/json
{
"customerName": "Taro Yamada",
"customerEmail": "taro@example.com",
"subject": "About my order",
"customerContent": "Hello, ..."
} customerName, customerEmail, and customerContent are required. If the project has a reCAPTCHA secret key, also send the reCAPTCHA token obtained on your form as recaptchaToken; requests without it are rejected.
7. Use AI drafts (optional)
- An organization owner registers an OpenAI API key in the LLM section of "Settings". This turns on inquiry summaries.
- Reply drafts follow the AI prompt (instructions for how drafts are written) and reply email template selected on the project. Inquiries registered from a web form (step 6) get a draft automatically. For inquiries brought in by email forwarding (step 5), use "Generate a reply with AI" on the thread page.
- Adjust the drafts by editing the AI prompt in "Templates".
OpenAI bills you directly for API usage. Without these settings, you can still manage inquiries and write replies yourself.
Troubleshooting
- You cannot log in, or cannot use the app after logging in: if you see the "under review" screen, your organization has not been approved for the beta yet (step 2).
- Replies do not arrive or land in spam: run the test send of the email account and check the SPF, DKIM, and DMARC records of your sending domain (step 3).
- Inquiries are not brought in: check that messages are forwarded to the receiving address in step 5 and that forwarding is enabled on the forwarding service.
- No AI drafts are created: inquiries brought in by email do not get one automatically (generate it on the thread page). Also check that the OpenAI API key is registered and that the project has an AI prompt and a reply email template selected (steps 4 and 7).
If that does not help, please reach us through the contact page.