◆ Amazon DynamoDB

Set up automated email response systems

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskConfigure the automated email system to send a 'welcome' email to new sign-ups within 5 minutes…+
Configure the automated email system to send a 'welcome' email to new sign-ups within 5 minutes of account creation. Include a link to our getting started guide.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore we activate the 'password reset confirmation' email, review its content. Ensure it…+
Before we activate the 'password reset confirmation' email, review its content. Ensure it clearly states what to do if the user didn't request a reset and includes a direct link to contact support, making it secure and user-friendly.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWe're setting up an automated email for failed payment notifications. I'm worried about sending…+
We need to set up an automated email for failed payment notifications, but I'm unsure about the right frequency and tone to avoid annoying users.
We're setting up an automated email for failed payment notifications. I'm worried about sending too many emails and annoying users, but also about not notifying them enough and losing revenue. Our finance team wants daily reminders, but I think that's too aggressive. What's the optimal frequency and tone for these emails to maximize recovery without alienating customers?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly manually sending follow-up emails for specific edge cases, like delayed order…+
I often find myself manually sending follow-up emails because our automated systems don't cover specific edge cases.
I'm constantly manually sending follow-up emails for specific edge cases, like delayed order fulfillments or unusual account activity, because our existing automated systems don't quite fit. This takes up valuable time. What habit should I change in how I design or review our automated email triggers to cover these less common but critical scenarios, so I don't have to intervene manually?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Amazon DynamoDB's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.