Category

Creating a Ticket Without an Email Address in BoldDesk

Updated:

In BoldDesk, an email address is required to create a contact or account. However, if a customer’s email address is unknown and only a phone number is available (reached out via phone call), you can use a workaround to create a ticket on behalf of the customer.

Workaround for Missing Email

When the requester’s email is not available: Create a contact using a dummy email address based on the phone number. Format: [email protected]

This allows you to associate the ticket with the contact while maintaining system requirements.

dummy email.gif

  • BoldDesk has blocked outgoing emails from the test.com domain to prevent bounce issues.
  • If you use a different domain as a placeholder, there is a risk of email bounce, which may block outgoing emails. In this case, please provide the email address so we can block the outbound email.

Need a Different Placeholder Domain?

If you require a domain other than test.com for dummy emails, contact BoldDesk Support at: [email protected] or BoldDesk Support portal.

They will assist in configuring an alternative domain safely.

Best Practices

  • Always use test.com for dummy emails unless otherwise approved.
  • Avoid using real domains to prevent accidental email delivery or bounce issues.
  • Document the dummy email format for your support team.

Frequently Asked Questions (FAQ)

1. Can I create a ticket without an email address?
Yes, by using a dummy email address such as [email protected].

2. Why is test.com recommended for dummy emails?
BoldDesk blocks outgoing emails from test.com to prevent bounce issues.

3. What happens if I use another domain?
Outgoing emails may bounce, and your email sending could be blocked.

4. Can I request a custom placeholder domain?
Yes. Contact BoldDesk Support at [email protected].

Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Comments (0)
Access denied
Access denied
Access denied
Access denied

No articles or sections found
No articles or sections found