Torch Project Management Search – Detecting Intent

Sunday, July 18th, 2010

Torch Project Management has an amazingly powerful search system. With the use of bucket selectors you can drill down into your data and analyze every aspect of your project. However, bucket selectors are often confusing to new users.

Torch now tries to detect intent on simple searches (searches without bucket selectors or boolean operators). For instance, if you searched messages for:

train movement info@acme.com mark@acme.com

You probably intended to search e-mails between "info" and "mark" for the words "train" and "movement". So, Torch rewrites this search request as:

train movement email:info@acme.com email:mark@acme.com

Additionally, if you searched messages for:

pinned track planning

You probably intended to search pinned messages for "track planning". So, Torch rewrites this search as:

track planning pinned:yes

Let’s say you searched events for:

uncompleted pinned Mark James

You probably intended to search for an uncompleted event that you have pinned that mentions Mark James. So, torch rewrites this search as:

Mark James complete:no pinned:yes

Many more examples exist, but obviously this will never be as accurate as when you use the bucket selectors yourself.

You might also notice (at times) an optional notice that says:

Did you mean "X"

This happens when Torch is less sure what you intended.

Heap CRM Search – Detecting Intent

Friday, July 16th, 2010

Heap CRM has an amazingly powerful search system. With the use of bucket selectors you can drill down into your data and analyze every aspect of your business. However, bucket selectors are often confusing to new users.

Heap CRM now tries to detect intent on simple searches (searches without bucket selectors or boolean operators). For instance, if you searched messages for:

fireplace receipt info@acme.com mark@acme.com

You probably intended to search e-mails between "info" and "mark" for the words "fireplace" and "receipt". So, Heap rewrites this search request as:

fireplace receipt email:info@acme.com email:mark@acme.com

Additionally, if you searched messages for:

James Doe invoice 1234

You probably intended to search messages associated to "James Doe" for "invoice 1234". So, Heap rewrites this search as:

invoice 1234 association:James Doe

Let's say you searched prospects for:

(509) 000-0000 customer

You probably intended to search for a customer with a particular phone number. So, Heap rewrites this search as:

phone:(509) 000-0000 type:customer

Many more examples exist, but obviously this will never be as accurate as when you use the bucket selectors yourself.

You might also notice (at times) an optional notice that says:

Did you mean "X"

This happens when Heap is less sure what you intended.