Resources
Example requests
A few ways to put agents to work.
You can ask for almost anything in plain words. These are good starting points; change the details to fit your store.
| Launch | Build a store for handmade candles with a warm, minimal look. |
| Catalog | Add a linen shirt in white and navy, sizes S to XL, at $45. |
| Orders | Fulfil all of today's UK orders with the cheapest tracked service. |
| Marketing | Create a 15% code for returning customers, valid until Sunday. |
| Insight | Compare last month's profit with the month before, and tell me what changed. |
| Design | Add a “Frequently bought together” section to every product page. |
| Going live | Is my store ready to go live? If it is, publish it. |
| Routine | Every morning at 8, tell me about anything that's down to 10 units or fewer. |
Troubleshooting
Quick fixes for common snags.
When something isn't working, telling agents what you see is usually the fastest fix. For the most common problems:
| Problem | What to do |
|---|---|
| Agents stopped replying | Your usage credits may have run out. Top up in Settings → Usage. |
| The preview says it's paused | Select Wake it up. Nothing was lost. |
| Checkout can't take payments | Add your Stripe key: a test key for the preview, your main key for the live site. |
| Emails aren't being sent | Check that your sending domain is verified and your store is published. |
| My domain doesn't show my store yet | Nameserver changes can take a few hours. Ask agents whether it's live. |
| A publish failed | Your live site is unchanged. Ask agents to fix the reason shown and publish again. |
| Something looks wrong after a publish | Roll back from the Publish menu, then fix it in the preview. |
| A model declined a request | Rephrase it, or switch to another model and send it again. |
Security & privacy
Your business and your customers, protected.
Payments run through your own Stripe account, so card details never touch Prezense, and your Stripe keys stay on the server rather than in shoppers' browsers. Every store's data is kept separate, every site uses HTTPS, and traffic is screened for attacks before it reaches your store.
Agents can only change your store with your approval, never save passwords or keys to memory, and access keys used to import from another platform are used once and not kept. You can download your data at any time, and when you close a store it's permanently deleted after 90 days.
Support
Help when you need it.
Start by asking agents: they can see your store and fix most problems on the spot. The troubleshooting table above covers the usual snags. If you're still stuck, email us at support@prezense.app and we'll help you get going.