When Generate fails, credits look wrong, or you imagine a workflow Rhinobird lacks, you need a support path that gets answers without endless back-and-forth. Rhinobird publishes direct contacts—phone 13378452864 and email support@rhinobird.ai—for issues and business messages. This article explains how to report defects effectively, how feature ideas are evaluated, and when self-help in Help Center should come first.
Before you contact support
Many incidents resolve without a ticket:
- Confirm sign-in via Login / Sign up and the same email that owns the job.
- Open History for delivery status and preview.
- Compare credit transaction details when a failure may qualify for return under membership rules.
- Retry once after refresh for upload or page load issues documented in Generation and Download Help.
- Check Pricing and plan status when Generate blocks for insufficient credits.
If those steps fail, gather evidence and contact support with one thread per incident.
Reporting product issues
- Subject line: Support — [short issue] — [company or email domain]
- Registered account email and sign-in method (Google or email).
- Tool or page where the issue occurred.
- Timestamp timezone included for the last Generate attempt.
- Expected vs actual behavior in one paragraph each.
- Screenshots or screen recordings without passwords or full payment card numbers.
- Whether the job appears in History; if failed, exact error text.
For credit disputes, note the cost displayed on Generate and whether the balance changed. Support aligns with Service Agreement task rules—polite, complete tickets resolve faster than angry one-liners.
Phone vs email
Phone suits urgent campaign blockers when email latency threatens a launch window. Email suits attachments, long reproduction steps, and finance questions needing written record. After a call, email a summary so staff can link notes to your account. International callers should state language preference early; prepare English tool names as shown on the UI.
Submitting feature ideas
Product teams prioritize ideas tied to measurable user tasks. Strong requests include:
- Problem — “We rebuild the same brief across five SKUs nightly.”
- Current workaround — “Copy Creative Requirements manually; duplicate History downloads.”
- Impact — hours saved, error reduction, revenue enablement.
- Scope — single tool vs account-wide; must-have vs nice-to-have.
Weak requests—“add more AI”—without scenario detail rarely advance. Feature ideas are not SLA commitments; support may acknowledge receipt without shipping dates.
Security and privacy in tickets
Never send passwords, one-time codes, or full card numbers. Redact client PII not needed to reproduce bugs. Upload samples only when rights allow; reference Privacy Policy if you need deletion of attachments after closure. Report suspected unauthorized account access immediately with History anomalies.
Enterprise and partnership messages
Seat licensing, partnerships, and invoices may share inboxes with support. Label subjects clearly—Enterprise, Partnership, Support—so routing stays accurate. Company background for external decks: About Us. Legal questions about data: Privacy Policy.
After support responds
Test suggested fixes on a low-cost proof Generate before scaling spend. Confirm returns in credit details when advised. Close the loop if reproduction steps change after a release so documentation stays accurate. Help Center articles update over time; your detailed tickets improve those updates.
Support works best with signed-in context, History facts, and clear subjects. Call or email official contacts, separate bugs from feature dreams, and read Service Agreement when credits or AI outputs are in dispute.