Give customers a richer, role-aware domain workspace for supported contact, privacy, nameserver, DNSSEC, and verification operations.
Extended Domain Interface is planned for the deeper domain tasks that benefit from a role-aware customer experience: contact changes, privacy, child nameservers, DNSSEC, and verification work where the domain supports them.
Registrant, admin, technical, and billing roles
Privacy, child nameservers, and DNSSEC where supported
A safe experience outside compatible domain management
See the practical result for your team and your customers before diving into the service details.
It is designed to give customers more useful domain controls without hiding the registrar and TLD limits that determine what a specific domain can do.
Start with a clear offer built around the services your business can provide.
Turn the purchase into a service with the right information and a clear next step.
Give customers and staff an easier way to find service details, guidance, and supported controls.
Handle renewals, changes, and support with a clearer view of what the service needs next.
The value of the service does not stop at the first order. These are the parts designed to make selling, supporting, and using it feel more straightforward.
Start with the services your business can confidently provide, then present them as a clear choice instead of a confusing list of options.
Manage supported registrant, administrative, technical, and billing contacts with designated-agent context.
Show the choices that fit the service, so customers are not asked to make sense of options that do not apply to them.
Product, customer, service, invoice, and renewal information remain together in the WHMCS workspace your team already knows.
The experience is designed to make the path from purchase to a working service easier to follow for everyone involved.
Expose eligible privacy controls, nameservers, and child-nameserver operations.
Your team can see what is in progress, what needs review, and what is ready for the customer.
Important changes are checked before they are treated as complete, reducing the chance of a support issue later.
A good service should answer the common questions before they become a support request: what do I have, what do I do next, and where do I go?
Support eligible DNSSEC plus RAA or IRTP verification resend workflows.
Service status, guidance, and supported access help customers move forward without leaving the client area they know.
The parts that need extra care remain protected, while customers still get a clear path to the help and controls they need.
Customers grow, renew, and change their minds. The service should make those moments easier to handle, not turn them into clean-up work.
Retain a useful, non-breaking experience for domains outside compatible LogicBoxes management.
Your team has a clearer view of what a change means before it affects the customer’s service.
The page makes clear which choices are available for the service, so customers and staff can act with confidence.
A planned interface whose available actions depend on registrar, TLD, supplier, and connected-account support.
Capabilities depend on the connected ResellerClub/LogicBoxes account, product, geography, and—where applicable—TLD. Supplier-changing actions are designed to be reviewed and reconciled before WHMCS reports success.