Darren Patterson

And so one of them, which is not the example you described, Corey, but one of them is like on a regular basis.

And that regular basis might be every one minute or it might be every 10 minutes or every day I'm going to do something.

So that's a pretty straightforward way of kicking off work on a routine schedule.

so depending upon the software applications you're working with working with obviously google docs here it requires that so every five minutes this is kind of checking and of course i can kind of fine-tune that as much as i want but it's it's checking uh google docs to say hey are there any uh files

that I have not yet processed.

That's kind of a key phrase that actually kind of people might not always understand the nuance, but that I haven't yet processed that's in the ready for planning folder.

So I'm basically constantly pulling this to see if it's ready to go.

That's one way to kick off work.

The second other way is slightly technical, but it's a web hook, but it's an instance.

It basically means that other application has the ability to send information my way.

And I might have wired this up to my e-commerce front end, and it's immediately going to send information to this scenario and kick off that agent and interact with it.

And then the last one, and the super simple way to do what you were working on, Corey, is...

We actually have a concept of mail hooks.

Basically, I can have a set up a magic email address that's like, hey, to-do list later.

I just give it that contact in my phone, and then I would just send it to to-do list later.

Every time it receives an email, this is kind of old school technology.

We don't have the fax option, but we do have the email option.

So if it kicks off based upon a new email, it's a particular address.

That's all.

Well, we got some investment advice, I think, there from Grant.