Ask your locations what you could never ask before

Out of all my locations, find the one a customer would call the spot near the station. Match on name and address, show me the two or three that could plausibly be it, and lay out what actually tells them apart. If two are close enough that I could pick the wrong one and end up editing the wrong storefront later, stop and ask me which, don't just grab whatever sits at the top of the list.

I'm going to describe one of my places in my own loose words, like my little one with the corner terrace, and I want you to tell me which location I mean, fast. Give me the closest match by name, and if a couple of them could fit what I said, show me both and ask me to confirm instead of guessing. I'd rather you say you're not sure than send me to the wrong branch.

Pull up my restaurant's full profile the way Obenan manages it and give me the honest one-page version: name, address, category, contacts, the lot. Then do the part I can't do from the inside, tell me what a stranger on Google would find thin, missing, or confusing, and which single gap is most likely quietly costing me walk-ins. Separate what's actually stored from what's your read, and don't invent a value to fill a blank.

Open the full profile for the location we just landed on and let me eyeball it before I build anything on top of it. Read the name and address back to me, and if that's not the exact place I meant, stop right there and say so, I don't want to spend an hour editing the wrong branch. And don't let a tidy-looking profile fool either of us: this view can't prove the integrations behind it are actually live, so flag that rather than assume.

Lay out every location on my account and organize it the way I'd actually picture it in my head, grouped by city or by the naming pattern I clearly use. Then do the thing that saves me from myself: point out any two names so close I could easily act on the wrong one, because that's how a change meant for one shop lands on another. Tell me which pairs to be careful with. This is just my Obenan list, so don't treat it as a count of every real-world door I have.

Read my cafe's weekly opening hours back to me, but do it as if you're a hungry customer standing at my door at 8pm on a Tuesday. Walk the week day by day and flag anything that would quietly turn someone away: a gap in the middle of the day, a suspiciously early close, a split that looks like a typo, a day that's just blank. Tell me the one fix that would rescue the most missed visits. And be clear these are my regular hours only, so holiday and one-off closures aren't in this picture.

Look at the attributes on my profile, the amenities, accessibility, payment and service options, and answer the question that actually keeps me up: what am I silently telling people I don't offer? Show me what's set, then the ones sitting there unset that a customer reads as a flat no, like wheelchair access or card payments. Point me to the single blank most likely to make someone pick somewhere else. And don't guess a blank means no, flag it as unconfirmed so I can fill in what's true.

Show me the discoverability keywords being tracked for my place, then be honest about the bet they're making on my behalf. Which are near-duplicates doing the same job twice, which are off-brand or so generic they'll never single me out, and what obvious money-maker is clearly missing given what I actually do? Hand me the one change that would sharpen my targeting most. And keep it straight: these are tracked target terms, not proof of what people really search or where I rank.

Give me the real map of where my business actually shows up across the directories Obenan tracks, and more importantly where I'm missing or out of sync. I'm most worried about the spots where I'm quietly saying two different things about myself, since that's what makes a customer trust nobody. Rank what to chase first by how much it dents trust. Treat presence and sync status as a signal to investigate, not a promise that every listing out there reads exactly right.

Grade my profile the way you'd judge a storefront on opening morning, using the fields and social links Obenan can actually see. I don't want a lecture, I want the smallest, fastest fixes that close the biggest trust gaps, the blanks that make a first-timer hesitate. Order them so I can knock out the highest-impact one in five minutes. Don't invent a value to make a field look full, and be clear a fuller profile is about trust, not a guaranteed bump in rankings or sales.

Here's what I really do in one honest sentence: [describe your business the way you'd tell a new neighbor]. From the Google categories actually available to me, find the one that quietly decides who Google shows me to: which single primary fits best, and which couple of secondaries are worth adding without muddying who I am. If my sentence could point at genuinely different categories, don't pick for me, show me the fork and ask. Being on the list doesn't make a category right, or mean it's applied yet.

Show me how my locations are actually grouped in the account: names, how many sites sit in each, and where. What I really need is which single group cleanly means 'all my city-center cafes' so when I run a campaign I hit exactly those and nothing stray. Flag any groups with overlapping or confusing names that could trip me up, and be honest that a group's name and count are only a hint, so tell me to open the group and confirm who's really inside before I trust it as my target.

Before I fire a change across a whole group, I need to know it's exactly who I think it is, not branches I forgot about. Show me its real headcount and members, and match that count against what I carry in my head: if it's off, something's wrong. Turn the location IDs into real branch names where you can, and say so when you can't instead of guessing. Then give me a yes or no on using it as my scope, and be honest this is who's in the group right now, not proof they share the same setup, so branches can differ.

Am I actually making my customers happier, or just telling myself a nice story? Take my restaurant and set the last three months against the three before: the star mix, the reply rate, and what people keep bringing up in their own words. Then name the one theme that genuinely moved, good or bad, and the single change it points to. If there aren't enough reviews to call it a real trend, tell me straight, and don't pin it on one cause, just show me what shifted and what's worth acting on first.

Show me what my happiest customers can't stop raving about, in their own words. Pull the best reviews for my cafe, find the two or three things they keep falling for, the exact phrases and moments, and turn it into one short "this is what we're famous for, do more of it" note I can hand the team Monday morning. Just remember these are only my glowing reviews, not the whole room, so don't let them speak for everyone, and if it's only a handful, say so plainly.

Show me the reviews that should actually keep me up at night, worst first, and sort them into two piles: the ones where a real person is hurting and needs me to reply like a human today, and the ones pointing at a real kitchen or service problem I have to fix at the source. Tell me the pattern and the one fix that would silence the most of them, not just a wall of complaints. Treat each as somebody's side of the story, not proven fact, and if it's only a few, don't blow a one-off into a crisis.

Before I ever let a robot answer reviews in my name, show me plainly what Obenan can put on autopilot: which reply modes keep a human template in the loop, and which let AI post publicly with nobody checking. Then tell me straight which star ratings I should never hand to unsupervised AI, and sketch one safe starting policy I'd be comfortable signing. Don't build anything, and don't pretend these settings know whether they fit my brand.

I'm a little nervous about what my review automation is already doing without me watching. Go through every auto-reply rule on my account and find the one that scares me most: the broadest reach, the lowest star ratings, or AI posting publicly with no human in the loop. Tell me which single rule I'd be embarrassed to explain to a customer, and why. Just read them, change nothing, and remember this shows what's set up, not proof of how any real review got answered.

Take my newest auto-reply rule, or whichever one I point you at, and explain it back to me in one plain sentence I'd happily sign my name to: where it applies, which reviews set it off, whether a human or AI writes the reply, and who's watching. Then flag anything vague or broader than I'd expect before I trust it. Just reading it can't prove it ever fired right, so tell me what you can't actually see from here.

Pull up every saved review-reply template I've got and read them the way a suspicious customer would. Which sound canned or robotic, which could land me in trouble if they went out on a complaint or in the wrong language, and which few are genuinely safe to lean on for a supervised auto-reply? Rank them and name the one I should rewrite first. Don't send or attach anything, and remember: having a template doesn't mean it fits every situation.

Before I build anything, tell me if a new auto-reply rule would collide with one I already run. Here's what I'm weighing: [say it plainly, like 'AI answering five-star reviews with no written text at my downtown cafes']. Scan my existing rules, find any review that two rules could both grab, show me exactly where they overlap, and rank the clashes by how badly a double or contradictory public reply would embarrass me. Change nothing, and don't assume a clean result covers automation outside Obenan.

Read my draft auto-reply rule back to me like a contract lawyer, not a cheerleader. Here's the rule I'm drafting: [describe it in plain words]. Catch every missing or wrong field, tell me the supervision mode it actually computes to (because I do not want it quietly landing on unsupervised AI), and hand me a clean corrected version I can look over. Write nothing and create nothing, this is just a sanity check, and passing here still doesn't prove it won't clash with my other rules.

Rehearse this auto-reply rule for me before it goes live. Here's the rule: [describe it plainly]. Walk me through exactly what it would do if I switched it on: which locations and ratings it grabs, whether a human template or AI writes the reply, the supervision mode it lands on, and any existing rule it would clash with. Finish with one honest 'here's what would happen' line, and touch nothing live. A rehearsal can't promise the replies read well or ever reach the customer, so say so.

Beyond Google, which review sites can Obenan actually watch for me, and which will even let it post replies back? I'm widening what gets tracked for my restaurant. Walk the supported sources, flag which allow more than one page link and which support replies, then tell me the single source I'd be foolish not to add for a place like mine, and why. I'll need each site's public page URL to connect it. Don't connect anything, and don't assume I already have a live profile everywhere.

Show me every review channel I'm connected to right now, then find what's quietly broken. Which connections have gone inactive or thrown an error, which look like duplicates of the same page, and which sources from the catalog am I not watching at all? Point me at the one dead or missing channel costing me the most visibility, and why. Connect and disconnect nothing, and be honest: a live connection here isn't proof the reviews are flowing in fresh or complete.

There's one review I keep thinking about: [paste it, or point me to it]. Read it properly, catch what the customer is really upset or delighted about, and write a reply that sounds like me, not a corporate robot. Show me the exact words before anything goes public, and if I've already replied to this one, warn me loud, because this overwrites what's there. Don't invent an apology or a refund I never offered, and once it posts, read back what actually went live.

I want Obenan keeping an eye on another place people leave reviews about me, here's the page: [paste the https link]. Work out which of my locations it belongs to and which kind of source it is, and if the link looks off or I'm already tracking it, tell me before we go further. Show me exactly what you'll connect and to which location, wait for my approval, then confirm it actually saved. And be straight with me: connecting it doesn't mean old reviews show up instantly or ever backfill.

I'm thinking about cutting one of my connected review sources loose. Before you touch anything, show me exactly which connection it is, which location it feeds, and what I'd stop seeing once it's gone, because I don't want to blind myself by accident. If more than one thing could match, stop and ask me. Wait for my clear yes, then disconnect it and confirm it's really gone. And tell me plainly: this only stops Obenan tracking it, it doesn't wipe those reviews or my profile on the actual platform.

I'm done hand-writing replies to my Google reviews. Here's what I want: [describe the goal, like quietly thank every 5-star and flag the angry ones for me]. Build a rule from that using only ratings and conditions that really exist, then preview it before it's live so I can see exactly which ratings and locations it'd cover and whether it'd post publicly on its own or just flag reviews for me. Show me the final rule, and if it ever posts without my sign-off, say so loud. Nothing goes live without my approval.

Change one of my auto-reply rules to do this: [describe the new behavior]. First show me how the rule works right now, field by field, then a clean before-and-after so I can see exactly what shifts. If the change widens which locations or ratings it hits, or lets AI post publicly on its own, flag it in bold, don't slip it past me. Wait for my approval before saving, then read it back. And remember: this only changes what happens next, it won't touch replies already posted.

I'm tempted to delete one of my auto-reply rules, but talk me out of it if this is a mistake. Show me exactly what it targets, which ratings and conditions set it off, and whether it's posting on its own right now. Then tell me straight whether narrowing or editing it down would be safer than killing it, and be honest about which options I really have. Only delete after my explicit yes, and confirm it's gone. Deleting stops it going forward, but it won't undo replies it already posted.

Skip my star average for a second. Read the mood in my reviews right now, then set it against how my rating and review numbers have moved versus the stretch before, and tell me the honest verdict: is my restaurant quietly warming up or cooling off, and what's the one theme most likely driving it? If there aren't enough reviews to call this a real shift instead of noise, say so plainly instead of dressing a hunch up as a trend.

Out of everything people bring up in my reviews, show me the handful of moments that actually decide whether someone leaves happy or annoyed, ranked by how hard they push the mood, with each one's rating and how much more or less it's being raised than before. Separate what a crowd keeps repeating from one vivid rant, then land on the single pain point I should fix first before it spreads.

My average rating looks fine, and that's exactly what worries me. Show me the full spread of stars now against the stretch before, and tell me the uncomfortable part: are my threes and fours quietly drifting down, or are the fives and ones pulling apart into people who love me and people who feel burned? Then tell me which of those two is the bigger reputation risk, and why my average is hiding it from me.

I get the feeling I'm a different business depending on which review site you land on. Compare how I show up across every platform my reviews come from, keeping each site's review count separate from its actual rating and satisfaction, and find the one channel where my story suddenly turns sour. Then tell me which to go fix first, without pretending the crowd on each site is the same kind of customer.

Tell me the real words customers keep using about me, in their language not mine, split into the ones that make me proud and the ones that sting, ranked by how often they come up. Point at the one word that shows up far more than I'd expect, because that's the story forming about me. Keep this about how people describe me in reviews, not what they type into Google, and tell me the single word I should lean into or get ahead of.

Pull my whole reputation picture together: total reviews, the mix of happy and unhappy, the rating trend and how fast new reviews are landing, then show me where those signals argue with each other, like the mood holding up while the rating quietly drifts. I don't want a tidy summary, I want the contradictions. End with the three sharpest questions those clashes raise that I should chase down before I change anything.

Take the pain buried in my reviews and the fixes the AI already drafted from them, and sort them into what to fix today, what to dig into before I commit, and what to just keep an eye on for now. Rank by how much it's actually hurting me and how solid the evidence is, not by what's easiest. And be upfront that these are smart suggestions drawn from what people wrote, not proven fixes, so I know what's still on me to verify.

Let me read the real reviews sitting behind the summary, not just the numbers. Pull the ones that actually matter, say the angriest recent ones, or a specific sting like slow service, and show me enough of each to feel what the customer felt. Then tell me honestly whether these back up the overall story or fight it. Focus on what they said, and don't single anyone out by name or drag in personal details.

Everyone keeps telling me my Google views are up, but views don't pay the bills. Look at how people found my restaurant over the last few months against the months before, and find the one place attention is leaking: are the folks who see me actually calling or asking for directions, or scrolling right past? Give me the ratios, not just totals, and be straight that this is profile activity on Google, not proof that anyone actually walked in and bought something.

Here's what actually keeps me up at night: am I growing because brand-new people are discovering me, or just because folks who already know my name keep Googling me? Compare branded searches against discovery searches month over month for my business, tell me which way that mix is drifting, and what it means for whether I'm building a reputation or quietly coasting on one. Read the search-type split only, don't pretend you know why any single person searched.

Show me the actual words strangers type into Google that surface my cafe, and group them by what those people really want, not some flat alphabetical list. Then find the quiet gap: something people clearly search for that my profile barely speaks to. Name the one topic I should be talking about way more. Just remember these are search appearances, not clicks or sales, so frame it as where I show up, not proof that anyone came through the door.

I want the uncomfortable mirror. Pull the words my customers actually use about my place in their reviews, the good and the bad, and set them next to how I describe myself: my business in one honest sentence is [describe it]. Show me exactly where those two stories don't match, because that gap is what strangers end up believing about me. If there aren't enough reviews to be sure, say so straight instead of guessing, and don't mix up review words with what people actually search.

One word keeps popping up in my reviews and I honestly can't tell if it's a real problem or just one loud night. The word that's bugging me: [paste it]. Pull the actual reviews behind it, read them side by side, and tell me straight: is this one bad evening someone won't let go, a few separate issues wearing the same word, or a real pattern I need to fix this week? Go only on the reviews in front of you, don't guess about the ones you can't see.

Give it to me straight: how easy am I actually to find online right now? Walk me through my discoverability score and what sits underneath it, then stop dancing and name the single weakest spot holding me back, plus what I should dig into next. Use the competitor context if it's there. And be honest with me, this is a health signal about how findable I am, not a promise about where I rank on Google or how many people walk in.

I don't want a big scary project, I want wins I can actually knock out. Break my visibility into the concrete pieces that build it, show me which ones are helping, which are dragging me down, and which are just plain missing. Then hand me the three smallest, easiest-to-undo fixes first, the ones with the least risk and the fastest payoff. Keep it honest: knocking these out lifts the score, it doesn't guarantee a ranking or more customers.

Walk my numbers month by month and answer one thing: do the people who see me on Google actually go on to ask for directions, or do they just look and drift off? Work out that view-to-action rate for each month, then point to the exact month something quietly shifted, up or down, and tell me what I should go check around that month. Just flag when it moved, don't pretend you know why, and remember this is online activity, not proof anyone walked through my door.

Be blunt about my Google posting: is it dead quiet, the same thing over and over, or actually healthy? Look at how often I post, the mix of what I'm putting out, and how long it's been since the last one, then give me a one-word verdict and the single content gap I should fill next. Keep me honest: this only counts how much and how recently I've posted, not whether Google delivered it, a soul saw it, or anyone came in because of it.

Before I trust a single Google number you show me, tell me the truth about the plumbing: is my business actually connected to Google right now, or have I been staring at stale data? Check the connection for my business and say it in plain English. If it's broken, hand me the simplest reconnect link and what to click, nothing technical. And be clear that a healthy connection just means the pipe is open, not that every future sync or update is guaranteed to go through.

My Google category never quite matched what I actually do, and I think it's quietly costing me customers. Here's my business in one honest sentence: [describe it]. Work out the primary and secondary categories that truly fit, using only Google's real category list, then show me exactly what you'd add and what you'd drop before you change a thing. Wait for my approval, and be straight that a better category helps me get found but doesn't guarantee it.

There's stuff I genuinely offer and brands I genuinely carry that my profile stays silent on, and I'm done underselling myself. Here's the list I can personally vouch for: [name the services and brands]. Add them on top of what's already there without touching my existing ones, tidy up any obvious duplicate wording, and flag anything you're not sure I really offer. Show me just the additions before you apply them, and confirm nothing already there got lost.

I'm opening a new spot and I'm honestly paranoid about creating a duplicate of one I already run. Here's the new place in one line: [name, full street address, contact email]. Check my account for anything that looks like the same location first, then show me the exact identity card you'd create before you create it. Wait for my approval, and remind me this only sets up the Obenan record, it doesn't create or claim the Google listing.

Swap my regular weekly hours for these: [paste the new schedule]. Show me a clean day-by-day before-and-after, and here's the one that scares me: flag any day I've accidentally left off, because those get marked closed and I don't want to look shut when I'm actually open. Keep my holiday hours separate, and wait for my ok before you save.

Set my holiday hours: [name the dates and whether I'm closed or on special times]. Show me the exception calendar laid out date by date before you save, catch any fat-fingered date or a closure I didn't mean, and leave my normal weekly hours exactly as they are. Wait for my approval. And remember this becomes my whole set of holiday exceptions, so include every one I still want.

Replace the search terms I'm tracking with this set: [paste them]. Show me what I gain and, more important, what I lose by dropping the old ones, and flag anything branded, off-topic or duplicated that won't actually help me get found. Wait for my approval before you overwrite the whole list, and be honest that setting these doesn't guarantee I rank, get seen or get clicks.

Add these search terms and keep every one I'm already tracking: [paste them]. Show me only the genuinely new ones after you strip out duplicates, tell me which customer each one is really aimed at, and don't pretend adding a word means anyone actually searches it. Wait for my ok before you save the combined list.

Drop these keywords and leave everything else exactly as it is: [paste them]. Show me precisely which searches I'd stop targeting, and keep exact matches separate from anything that only looks similar so we don't accidentally cut the wrong term. Wait for my approval before you remove anything, and be clear this doesn't wipe past data or prove my visibility will drop.

Set the areas I actually serve or deliver to: [list the towns or regions]. Show me what gets added and what gets dropped, and flag the classic trap for me: am I about to tell Google I have no storefront when I really do have a physical shop? I don't want to hide my counter. Wait for my approval before you redraw the map, and remember this doesn't prove I'm licensed or found in every place I name.

My short blurb sounds like every other spot on the street and I want it to finally sound like mine. Here are facts I can personally vouch for: [list them]. Using only those, find the one honest thing that actually makes people pick me and lead with it. No invented awards, no 'best in town', and if a line isn't in my facts, drop it. Show me my current blurb beside your version, and wait for my approval before you save.

My long description is my one shot to tell people who we really are, and right now it's flat. Here's what I can actually back up: [list the real facts and what makes us us]. Find the one true thing that sets us apart and build the story around that, don't just list everything. Every sentence has to trace to something I told you: no invented history, no credentials I don't have, no promises. Show me the current text beside the new one, each claim tagged, and wait for my approval before you save.

My location labels have piled up over months and half of them don't mean anything anymore, so I can't group or report cleanly. Here's the clean set I want instead: [list them]. Setting these replaces every existing label, so before you touch anything, show me exactly which labels I'd gain and which I'd lose, in case one I forgot is quietly holding a report together. And remind me straight: these are internal only, no customer ever sees them. Wait for my approval before you swap them.

The social links on my profile might be stale, and my real fear is one quietly points at the wrong brand or a page I've long abandoned. Here are the ones I want live: [paste the URLs]. Check each is well-formed and on the platform it claims, line them up against what's already there, and flag anything off-brand or just wrong. Be honest that a tidy URL doesn't prove the page is live or really mine. Show me the exact final set and wait for my approval before you save.

I need to fix a core identity fact on my profile, my business name or my opening date: [tell it exactly what's changing]. This is the stuff that has to be perfect. Show me a before-and-after of every field you'd touch, and if the new name reads like a different business than the one on file, stop cold and say so. Don't guess my legal name or open date from marketing. If an opening date's already set, tell me it can't be overwritten. Wait for my approval before you save.

A wrong phone number or dead website on my profile means lost customers, and I want to be sure mine are right. Update the ones I give you: [phone, website, and/or email]. Show me each old value next to the new one so I can see exactly what's being replaced, flag anything that looks like a typo or points somewhere that isn't me, and don't fill in a field I didn't give you. Wait for my approval before you save the change.

I need to change my location's status, whether that's new regular hours, temporarily closed, or permanently closed: [tell it which, and the hours if any]. Permanently closed is the one that scares me, so treat it as a serious, hard-to-undo move, not a routine edit. Show me my current status and hours next to the exact change, spell out what customers will see, and never assume I'm closed just because hours are blank. Wait for my explicit approval before you save.

My profile's amenities, accessibility, and payment options are probably out of date, and a single wrong one, like 'wheelchair accessible' when I'm not, can turn someone away or leave them stranded at my door. Here's my honest checklist of what's actually true today: [list what you actually offer]. Set only these, leave anything I didn't mention untouched, and don't infer amenities from my category or photos. Show me exactly what changes and what stays, then wait for my approval before you save.

I want to push a description and some keyword updates across several of my branches at once: [name the locations and what's changing]. But my branches aren't clones, so only apply what's actually true for each one and skip a branch where it doesn't fit. Remember the description overwrites and the keywords just get added. Show me a per-location preview of exactly what lands where, and wait for my approval before you apply anything, then confirm each one separately.

I want fresh photos on my profiles and my nightmare is one branch's cover ending up on another. Here's what I've got and where each should go: [paste the photo links, and which location plus role, like cover or logo, each is for]. Show me the exact photo-to-location-and-role map before anything uploads, flag any that look like the wrong brand, and remember cover and logo replace what's there. This gets queued for Google, not posted instantly. Wait for my approval first.

Walk my menu the way a hungry stranger reads it for the first time at my busiest restaurant, top to bottom. Where would they get confused, hit a dish with no price, or trip over a three-word description sitting next to a whole paragraph? Show me the duplicates and messy naming that make me look careless, keep my real menu separate from your fixes, and name the one thing to fix first. If this is the menu you can see through Obenan and not proof of what Google is showing this minute, tell me straight.

Before I build out my menu, show me the exact words my menu's actually allowed to use: the real list of cuisines, dietary tags, spice levels, allergens, and prep methods. Here's what I really want to know: which everyday terms I'd naturally reach for aren't on this list and would bounce when I try to save, so I don't lose half my menu to a typo I didn't know was wrong. Give me one clean valid example to copy, and be clear this is only the allowed vocabulary, not my real menu, so reading it changes nothing.

Here's my menu as a photo or PDF: [paste the link or attach the file]. Check it can actually be carried into a menu build safely, and be honest with me: this import step won't read or OCR the document, so tell me plainly what still needs my own eyes, which details you'll have to pull out by hand, and where you might guess wrong on prices or dish names. Hand me the accepted vocabulary and the structure to fill, confirm nothing gets written yet, and tell me the one thing I should double-check before we build.

Let's finally turn my menu into a proper Google menu. Here's my menu: [paste a link or attach the photo]. Read it yourself and don't invent a single price or allergen you can't actually see, ask me if anything's unclear, then show me the full menu preview before you create it. If I already have a menu, stop and tell me instead of overwriting. And be honest that this gets queued for Google, it doesn't go live the second you hit save.

I just want to add a couple of things to my menu without disturbing the rest of it. Here's what's new or changed: [paste the dishes and prices]. Match them to my current menu by name, then show me the merged result and prove every other dish is still exactly where it was, before you save anything. Wait for my ok. This only adds and updates, so nothing I leave off this list should disappear.

This uploaded menu is my new source of truth, make it the menu of record. Here it is: [paste a link or attach it]. Before you overwrite anything, show me a clear diff: every dish that gets added and, more important, every single dish that would disappear, so I never quietly lose one. Only remove things if I explicitly say so, and wait for my approval. And remind me the change queues for Google, it isn't instant.

Get rid of exactly one whole section of my menu. The section I want gone: [name it]. Before you delete a thing, show me every dish that would vanish along with it, and if more than one section shares that name, stop and refuse rather than guess which one I meant. Wait for my approval, then tell me what's left. And remind me this can't be undone from here.

Take one dish off my menu for good: [name the dish]. Before it's gone, show me exactly what disappears, its price, description and photos, and if I've got more than one dish with that name, don't guess, ask me which section it's in. Wait for my approval, then confirm the menu afterwards. And be clear this can't be undone from here.

Get these dish photos ready to use, a link or a Google Drive or Dropbox share is fine: [paste the links or attach the photos]. Show me which ones you can actually accept before you stage anything, skip anything broken, and be straight with me: this only parks the images as hosted files, it doesn't touch my live menu. I'll attach them to the right dishes in a separate approved step.

Read back the Google posts I've actually got set up across my locations and tell me what my content really looks like from the outside: which themes I lean on until they go stale, and the tired ideas versus the ones worth reviving. Here's what unsettles me: flag the posts whose status isn't a confirmed live state, because scheduling a post isn't the same as it going live. And don't read the dates as publish times, they're just when the automation started. Then pick the single best idea to bring back.

Before I write a single Google post, show me in plain English what actually counts as valid so I don't get quietly rejected on a technicality. Here's my campaign idea: [describe it in a sentence]. Turn the real allowed post types, buttons, schedules, and languages into a short cheat sheet, then flag anything in my idea that won't fit those options, and give me one clean version built only from what's allowed. If my idea needs something Google's rules just don't offer, tell me straight.

Walk my whole Google post queue with me and catch the landmine before it goes live. Pull everything lined up across my locations and find the real problems: two posts stacked on the same spot the same day, near-duplicate titles, an old promo that shouldn't still be scheduled, anything paused I probably meant to run. Tell me the single thing to fix first and why. And remember, queued isn't published, so don't tell me anything already went out.

I need the truth about my latest Google post: did it actually go live everywhere, or did some locations quietly fail? Go location by location and split them into genuinely live versus stalled or failed. Count a location as done only if the log literally says done, no benefit of the doubt. Then tell me exactly which locations I still need to chase, and if the failures cluster around the same spots, point that out so I fix the root, not the symptom.

I want to stop a scheduled Google post before it causes trouble, but show me what I'm touching first. Find the post I mean, tell me its current state and exactly what pausing will and won't do, and be straight with me: pausing stops future delivery but can't pull back anything already live on Google, and this workflow has no permanent delete. Show me the exact pause you'll apply and wait for my approval before you change a thing. Once I say go, read the new state back to me.

Help me roll one campaign across a bunch of my locations at once without it blowing up. Here's the campaign in my words: [describe it, plus the locations or groups I want]. Build the batch, then do a dry run first: show me every post it would queue, the exact wording and timing per location, and flag any duplicates or conflicts before anything's real. Let me approve the exact batch before you queue a single post. And be honest, queued isn't published, so I'll check delivery logs after.

I want to put up a Google post about this: [the post, plus the button and any offer or event dates]. First check what I've posted lately so I'm not repeating myself or double-posting. Show me the exact per-location preview of the title, text, button, and image before anything queues. And be straight that queued isn't live: a post sitting in the queue isn't proof it published, so tell me how I'll confirm it actually went out. Wait for my approval before you queue it.

What's my real NPS story, location by location, not just one flattering headline number? Show me the promoters, passives and detractors behind it and the actual math, then tell me which single spot is quietly dragging the whole group down and which one's carrying it. And if a location has too few responses to really trust, say so straight instead of dressing up a score built on five people.

Give me the honest read on what my survey is really telling me, not just a tidy average. Put the ratings and the answer breakdown next to the keywords and sentiment coming out of the short answers, and show me where they clash, like people scoring me high while the sentiment underneath runs lukewarm, or the reverse. Keep it privacy-safe with no raw individual answers, and if a theme is only a handful of voices, call it a hint, not a verdict.

Here's what's actually on my mind right now: [my real question, like "why are dinner guests leaving unhappy"]. Go through my surveys and tell me straight which one is even built to answer it, based on what each one actually asks, and which ones can't touch it. Don't just list them all. Point me to the single survey worth opening for this, and remind me that a survey sitting there isn't the same as it holding real answers yet, so I don't get ahead of myself.

Look at when my survey responses actually landed over the last few months and tell me if the rhythm looks off. I'm not after what anyone said, just the pattern: a sudden burst that smells staged, or a dead stretch where responses just dried up, maybe a broken link or a QR code nobody scanned. Individual answers stay private here and that's fine. Just point me to the one gap or spike that's worth me chasing down with a real question.

It's month-end and I've got an approved report to deliver, so pull the row-level answers for my survey over last month that I'm actually cleared to see. This is real people's personal feedback, so handle it with care: give me a clean, report-ready summary instead of splashing everyone's raw answers back into our chat, and flag the handful where a customer clearly wants me to follow up. And if my session isn't allowed to export this, just tell me plainly.

I want a report that actually proves something to my boss, not another PDF nobody opens. Before I set anything up, show me what Obenan can really report on: the report types, how often each can run, the file formats, and which sections exist for the type I have in mind. Here's what I'm trying to prove, in one honest sentence: [describe it]. Match my goal to the one setup that fits, flag anything the data can't back up, and don't invent a section that isn't really there.

How many reports are quietly running in my name right now, and are any of them the same thing set up twice? Walk every report schedule on my account, group them so the overlap jumps out, flag the stale or forgotten-looking ones, and tell me which existing one is closest to what I actually need before I spin up yet another. And remember: a schedule sitting in the list is no proof it ever ran, so don't call one healthy just because it's there.

Before I change a report I set up, read it back to me plainly so I don't touch the wrong one. The one I mean: [its name, or describe what it covers]. Tell me which locations it hits, its type, how often it runs, its date window, the file format, its sections, how many people receive it, and whether it's live or paused. Keep the recipients private, just give me the count, flag anything half-finished or surprising, and remember this is the setup, not proof it ever sent.

Who's actually getting my report, and is anyone on that list a person who shouldn't be, like a colleague who left or a personal address that slipped in? The report I mean: [its name, or describe what it covers]. Show me the recipients Obenan has, but keep every address masked, I don't need full emails to spot a problem. Count them, flag any duplicate or anything out of place, and be honest that a masked address is a clue, not a confirmed identity, so tell me what I'd still need to check myself.

I need to know if my report is actually reaching inboxes or just quietly failing. The report I mean: [its name, or describe what it covers]. Build me a timeline from its delivery records over the last few months, and draw a hard line between 'the file got made' and 'the email actually went out', because those aren't the same thing. Keep every address masked. Call out any repeating failure or a stretch where nothing sent, and tell me plainly which runs I can trust as delivered and which I can't.

My report didn't show up and I don't want to fall down a rabbit hole. The report I mean: [its name, or describe what it covers]. Pull the safe, redacted snapshot of its current state and its latest delivery attempt, tell me in plain words what most likely happened, and give me the single smallest next step to try, not a checklist of ten. Don't expose any emails or internal guts, and if the snapshot honestly isn't enough to know the cause, say so instead of guessing.

Before anything runs, sanity-check the report I want to set up: [describe it: which locations, what type, how often, what to include]. Tell me every field that's missing, wrong, or not actually supported, explain each fix in plain terms, and hand me back a clean, corrected version I'd be confident submitting. Don't build it, don't schedule it, don't email anyone, just catch the mistakes now so I'm not embarrassed later.

Let's do a full dress rehearsal of the recurring report I'm planning before I commit: [describe it: which locations, what type, how often, who should get it]. Show me exactly what it would end up set to, the locations and groups it'd actually cover, when the next run would land, how many recipients, and anything I picked that isn't really supported. Change absolutely nothing, this is a rehearsal, not a launch, and end by telling me the one setting most likely to disappoint me before I lock it in.

Before this recipient list ever goes on a report, check it for me: [paste the email addresses]. Tell me which ones aren't valid, mask every address in your answer so nothing sensitive sits in the chat, and flag any duplicates or obvious typos in the list I gave you. Be straight with me: a valid-looking address is no proof it's the right person or that mail will land there, so tell me what still needs a human eye.

I don't want to log into another dashboard, I want the actual file in my hand today. Build me the report I need, my reviews, how customers feel, or my Google activity, for my busiest spot over the last few months, and give me the download link. First show me exactly what you'll pull: the type, the location, the dates, the file, the sections, so I can fix a wrong setting before it's baked in. And be straight: this makes a file and emails nobody, right? Then run it.

I keep forgetting to pull my numbers, so set my busiest location up on a report that runs on its own every month. Before you create it, walk me through the setup: the cadence, the start date, the report type, the file, and the sections, so I can catch a mistake before it's locked in. If I've already got one by this name, tell me instead of making a twin. And be honest: creating this sends nothing today, and a schedule existing isn't proof a report will run later. Show me all that, then wait for my approval.

Put one of my report schedules on pause, I don't want it firing for a while, but do not delete it, I'll want it back. Before you change anything, show me the exact one you're about to pause: its title, what it covers, how often it runs, and what future runs would stop. Make sure it's the right schedule and not a lookalike. Then wait for my approval, pause it, and read it back to me as paused so I know it actually took.

Turn my paused report schedule back on, I want it running again. Before you flip it, show me which one you mean and when its very next run would actually fire, so I'm not surprised by the timing. If the next date looks fuzzy, tell me straight rather than guessing. Wait for my approval, switch it on, then read it back so I can see it's truly active again and not just half-on.

I'm tempted to kill one of my report schedules for good, but talk me out of it if I'm being rash. Before anything, show me what it is, what it covers, how often it runs, and its past runs, then tell me honestly whether just pausing it would be the safer call. If I still want it gone, wait for my explicit approval, delete it, and confirm it's really removed. And be clear: this stops future runs but does not erase reports it already produced or recall anything already sent.

Before I trust a single number from Obenan today, give me the ten-second gut check: are we actually connected right now and safe to pull my business data, or is something quietly off? Tell me straight what's working and what isn't, and if I need to reconnect, just the one next step. Never show me tokens or secrets. And if a green light only means we're connected, not that every location behind it is healthy, say so plainly.

I run several businesses through here and my biggest fear is working on the wrong one. Show me every account I can actually reach right now, then do the thing I'd forget to ask: point out any two that look dangerously alike, same name or near-identical name, so I don't confuse them. Don't switch anything yet. If the list might be cut short or you can't be sure it's complete, tell me straight rather than let me assume that's all of them.

Quick, before I do anything: which business am I actually pointed at right now? Tell me the account that every read and write would land on this second, and if it's not the one I think I'm in, stop me cold and say so before I touch a thing. If no specific account is loaded and we're just on my default, tell me that plainly too, because 'default' is exactly when I get careless and edit the wrong place.

I need to move into one of my client's accounts to work on it. Find the one I mean, then before you flip anything, show me whose account this really is, the name on file next to the ID and not just a number, and wait for my yes. If that name doesn't match the client I expect, or you can't confirm it for sure, warn me loudly before I commit, because that gap is the whole difference between helping my client and wrecking a stranger's business. Once I approve, switch me in and tell me where I landed.

I'm done working inside my client's account and I want to land safely back in my own default before I forget I ever switched. First show me where I am now and where clearing this will drop me, so it's obvious what's about to change, then wait for my approval. If I'm already on my default and there's nothing to clear, just tell me that instead of pretending you undid something. And be clear: this only changes what account I'm pointed at, it doesn't erase any work I already did.