Hi all, I have a few questions that I can't find an answer to.
1)If I'm working with a customer who has an e-commerce, and I have to send him the dedicated email, I've seen that I have to do things from the DNS, only how should I do it. That is, do I tell the customer that he must let me access the DNS? Or are there other things that can be done
2) Once a dedicated email is created, can I add the subdomain, and does it work? i.e. if the email info@store123.com is verified via DNS, can I send emails with info@send.store123.com? or does it not work?
3)Klavyio has payment plans, if I have 5 clients do I have to pay for each of my 5 clients the plan, or do I pay only for my account from which I manage 5 clients?
If you haven’t had a chance to review, I would suggest taking a look at some of our Help Center articles going over what and how to setup a dedicated sending domain to get a basic understanding:
In terms of working with your clients and who actually does the setting up on the backend, that would be something determined between yourself and your client. If your clients are comfortable allowing you access to their DNS and you’re comfortable making these changes, I don’t see why you can’t make an argument to set it up on their behalf. Else, you’ll want to instruct your client to make those configurations within their DNS on themselves.
If you’ve verified your sending domain with something like @store123.com, then you’ll want to stick to that as your sending domain. Any deviation such as using @send.store123.com would cause a misalignment since it’s technically not the domain you’ve verified.
Once again, this would go back to how you’re managing your clients. I don’t see why you would need to be the one to be paying for their subscription - unless you’re invoicing them for the monthly recurring charges. But typically each client will be responsible for the monthly subscription plan on each of their own accounts where you’ll simply be added as a user to perform work on the accounts.
If you haven’t had a chance to review, I would suggest taking a look at some of our Help Center articles going over what and how to setup a dedicated sending domain to get a basic understanding:
In terms of working with your clients and who actually does the setting up on the backend, that would be something determined between yourself and your client. If your clients are comfortable allowing you access to their DNS and you’re comfortable making these changes, I don’t see why you can’t make an argument to set it up on their behalf. Else, you’ll want to instruct your client to make those configurations within their DNS on themselves.
If you’ve verified your sending domain with something like @store123.com, then you’ll want to stick to that as your sending domain. Any deviation such as using @send.store123.com would cause a misalignment since it’s technically not the domain you’ve verified.
Once again, this would go back to how you’re managing your clients. I don’t see why you would need to be the one to be paying for their subscription - unless you’re invoicing them for the monthly recurring charges. But typically each client will be responsible for the monthly subscription plan on each of their own accounts where you’ll simply be added as a user to perform work on the accounts.
