◆ Amazon DynamoDB

Respond to user email inquiries

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 taskDraft a reply to Sarah from Acme Corp regarding her inquiry about transaction limits. Explain…+
Draft a reply to Sarah from Acme Corp regarding her inquiry about transaction limits. Explain our current daily and monthly caps and direct her to the FAQ for more details.
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 I send this response to the user experiencing slow data retrieval, clarify the steps…+
Before I send this response to the user experiencing slow data retrieval, clarify the steps they should take to diagnose the issue on their end. Make sure it's easy to understand, avoids jargon, and offers clear next steps if the problem persists.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA user just emailed, claiming their recent order disappeared from their history, but our…+
A user is complaining about lost data, but our logs show no errors, and I can't replicate the issue.
A user just emailed, claiming their recent order disappeared from their history, but our database logs show the transaction completed successfully and is present. I've double-checked, and I can't replicate the 'missing' order on their account. I'm afraid they'll escalate this. How do I respond without making them feel unheard, and what's the best next step to diagnose what they are actually seeing?
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 spending hours manually sifting through database logs and application traces to…+
I spend too much time manually searching logs to confirm user-reported data issues.
I'm constantly spending hours manually sifting through database logs and application traces to confirm user-reported data discrepancies, even when our monitoring shows green. This takes me away from development. What habit should I change to more quickly and reliably verify or refute these user claims, so I can focus on building features?
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.